How the Radius SDK builds an in-person fabric enabling the physical web.
What Started the Shift Towards Web Applications?
Today’s world is becoming increasingly contactless, from tapping your phone for payment to unlocking a door. Proximity-based technologies are revolutionizing how everyday consumers interact with the world. Devices are no longer just a communication protocol between consumers, they have become a way to interact with other physical devices as well.
Retailers have had to adapt to this change. In the past, in order to deliver proximity-based experiences to their consumers, they needed to have a native application. However, native systems are costly to develop and app downloads are a burden, turning the app into a barrier rather than an enabler.
Early movers, like Starbucks, recognized this and shifted resources from native mobile applications to more accessible web applications. Web apps are lightweight, faster to develop, and avoid cumbersome app store approvals. The only thing they lack is their ability to interact with surrounding physical devices. Browsers on iOS, such as Safari, restrict NFC and Bluetooth, limiting any web-based inter-device communication.
This changes with the release of the Radius Web SDK. For the first time, web apps on any platform can communicate with physical devices in an interoperable way.
This study explores how integrating the lightweight Radius Web SDK can optimize the Starbucks web app, transforming it into a frictionless portal that seamlessly syncs digital transactions with the physical storefront.
How the Web Broke the Native Standard
The Starbucks example highlights that native app downloads introduce severe friction points that disrupt the ideal consumer journey:
- Barrier to Entry: Downloading and installing the native app created a large barrier to entry for consumers looking to engage with the Starbucks digital ecosystem.
- Permissions Hurdle: The Starbucks app requires location permissions, which, if not granted, prevent consumers from completing essential functions.
- Sizing Problem: The Starbucks web application is 99% smaller than the native iOS app (233KB vs. 148 MB).
Recognizing these problems, Starbucks decided to make a change and developed a progressive web app alongside its native apps for their consumers. Starbucks achieved massive success, doubling daily active web users, and increasing web orders to near-parity with mobile app orders. This web-based solution, which accounts for over 30% of transactions, reduced onboarding friction, attracting busy, on-the-go customers.
Problems Remain in the Device-to-Device Consumer Journey for Web Applications
Even though Starbucks has seen an increase in mobile orders and app usage, consumers have still expressed shortcomings that could improve the retail experience.
- Location Services: Consumers have reported issues with the location services, stating that it struggles to identify their precise location in-store.
- Interactivity: Starbucks users have expressed a lack of personalization with the promotions offered in-store or on television.
- Pick-up in store: Long lines for pickup and long queues at the entrance discouraged ordering at busy times. Consumers should be rewarded for their online ordering; however, they are often left in the same line as those who did not.
The Solution: The Radius Web SDK Enables Interoperability for the Physical Web
The Web SDK enables data to be sent securely between the user’s browser and the store’s physical infrastructure. It allows the web app to establish immediate, high-trust communication with the retail location, facilitating instant menu discovery, streamlined checkout, and personalized loyalty experiences.
Until recently, there were not many solutions for web apps looking to connect the consumer’s device to the physical world. However, with the Radius Web SDK there is now a way for consumers’ physical context to be captured while offering a more seamless overall experience. LISNR’s Radius Web SDK can support all three concerns through a single proximity modality:
Key Feature Enhancements Enabled by the SDK
1. Frictionless Store Identification
By leveraging the Web SDK, first-time visitors can completely bypass both the login wall and invasive location services. Using inaudible tones, the SDK verifies a consumer’s presence on an as-needed basis without GPS.
2. A Unified, Single-Screen Checkout Payload
Web application restrictions to NFC and BLE create fragmented payment experiences at checkout. The Radius Web SDK allows the user’s payment data, custom order instructions, and reward points into a single interaction. One transaction bundles everything together, enabling a seamless payment flow.
3. Promotion Connectivity
Radius tones can be broadcast through any standard speaker including connected TVs, in-store displays, and drive-through menu boards.Whether they’re in-store or at-home, consumers can receive promotions with retailers building digital reward experiences around these interactions. Starbucks can now connect with its loyal consumers through multiple channels.
Sources:
Starbucks PWA. Scribd, www.scribd.com/document/386697644/Starbucks-PWA.
Singla, Manish. “UI/UX Case Study: The Starbucks App Revamp You’ve All Been Waiting For…” Bootcamp, Medium, 5 May 2024, medium.com/design-bootcamp/ui-ux-case-study-the-starbucks-app-revamp-youve-all-been-waiting-for-f51ebc8c507b.