Questions & explanations
1. What should a developer test when targeting Samsung Internet for their PWA?
A developer should test the PWA's service worker registration and cache functionality on Samsung Internet, as it may handle offline storage limits differently. They should also test the Badging API if used, because Samsung Internet supports it but with a slightly different icon shape. Additionally, test the install flow: ensure the install prompt appears correctly and the PWA launches in standalone mode. Check push notifications if implemented, as Samsung Internet uses its own push service. Also verify that the layout works well with Samsung Internet's default fonts and zoom settings. Finally, test the overall performance and any paid content integration, as Samsung Internet supports Samsung Pay for web payments. Doing these tests ensures a good user experience on Samsung devices.
2. What is one key difference between a PWA on Chrome OS and on Windows?
On Chrome OS, a PWA (Progressive Web App) integrates deeply with the operating system: it can be treated as a standalone app in the app drawer, receive notifications in the system tray, and even be assigned to keyboard shortcuts. On Windows, the PWA also runs in its own window but is not as tightly integrated; for example, it cannot use Windows' native notification center as smoothly, though it can send notifications via the web API. Chrome OS also supports launching PWAs from the search, the same as Android apps on that platform. Windows does not have a built-in PWA store, so installation happens only through Chrome or Edge. Both platforms allow offline use, but Chrome OS gives the PWA more of a 'first-class citizen' status.
3. If a user wants to use a PWA on desktop but prefers Firefox, what can they do?
If a user prefers Firefox on desktop but wants to use a PWA in a standalone window, they can currently try using a workaround. One option is to install the PWA using another browser like Chrome or Edge that supports installation, and then use that separate installed PWA while still using Firefox for regular browsing. Another option is to use Firefox to open the PWA in a pinned tab or as a separate window using the 'Open in New Window' feature, but this still shows the browser interface and is not a true PWA experience. Alternatively, the user can wait for Firefox to add full PWA installation support, which is expected in future versions. For now, the best solution is to use a compatible browser for the PWA.
4. What limitations does a PWA have that a TWA can overcome, and what trade-offs does a TWA introduce?
A PWA on Android cannot receive push notifications reliably when the browser is closed, because Android kills background service workers aggressively. A TWA (Trusted Web Activity) can use native push services to wake up the app. Also, a PWA cannot access all Android APIs, like Bluetooth or NFC, while a TWA's native wrapper can call those APIs and pass results to the web page. However, the trade-off is that a TWA requires a separate Android project, signing, and submission to the Play Store, which adds development and maintenance work. Additionally, the TWA's web content is still subject to Chrome's limitations, so some web APIs may not work. The TWA also adds a small download size compared to a pure PWA.
5. How do PWAs on desktop handle updates compared to native desktop apps?
PWAs on desktop update automatically without user intervention. When the user visits the online version of the PWA, the background service worker checks for a new version of the app files. If a new version is available, the service worker downloads it in the background. The update is applied the next time the user opens the PWA, or immediately if the previous session is closed. This is different from native desktop apps, which often require manual downloads or trips to an app store. However, some PWAs show a 'Update available' prompt to let the user decide. The update process is seamless and does not need installation wizards. Native apps usually need to be downloaded again or use an internal updater.
6. How does Firefox's approach to PWAs differ from Chrome's?
Firefox's approach to PWAs is more cautious and focused on privacy. While Chrome aggressively promotes PWA installation with banners and a dedicated install button, Firefox on desktop does not prompt installation at all. Firefox also does not support some PWA features that Chrome does, such as the Badging API and the ability to run PWAs as separate apps on desktop. On mobile, Firefox Android supports installation but with fewer features than Chrome Android, like no push notification support. Mozilla argues that some PWA features could reduce user control, so they implement only those that respect privacy. This makes Firefox less feature-rich for PWAs but more aligned with its privacy goals.
7. Why might a PWA work differently on Samsung Internet compared to Chrome?
A PWA might work differently on Samsung Internet compared to Chrome because each browser has its own implementation of web standards and may support different sets of APIs. For example, Samsung Internet has its own rendering engine (based on Chromium, but with custom features) and may handle service workers or storage differently. Some PWAs that rely on the Payment Request API might behave differently because Samsung Internet supports Samsung Pay integration. Also, the look and feel of the installed PWA, such as the splash screen and icon badge, can vary. Developers should test their PWAs on multiple browsers to ensure consistent behavior, as Chrome is the most common but not the only one.
8. What additional PWA feature does Samsung Internet support that Chrome on Android does?
Samsung Internet supports the Badging API, which lets a PWA display a numbered badge on its icon to show unread notifications or updates. Chrome on Android also supports this now, but Samsung Internet was one of the first to implement it. Samsung Internet also supports the Navigation Preload API for faster service worker startup, and it has a built-in 'Install Apps' feature that can suggest PWAs. Additionally, Samsung Internet allows PWAs to be installed directly from the browser without needing Google Play Services. However, Chrome has a larger user base and more advanced developer tools. Both browsers support core PWA features like offline and push notifications on Android.
9. How does a TWA allow a web app to access more Android features than a PWA?
A TWA (Trusted Web Activity) uses an Android app wrapper that can include native code to request permissions and use Android APIs. For example, the wrapper can register for push notifications using Firebase Cloud Messaging, which a standard PWA on Android cannot do without a service worker that may be restricted. The TWA can also access the device camera, GPS, and file system through the wrapper, while a PWA must rely on web APIs that are sometimes limited. However, the web content inside the TWA still runs in Chrome, so not all Android features are available directly in the web page. The trade-off is that the developer must maintain both the web app and the Android wrapper.
10. In what situation would a developer choose a TWA over a PWA?
A developer would choose a TWA (Trusted Web Activity) when their web app needs features that a standard PWA cannot provide on Android, such as reliable push notifications, background location updates, or integration with Android's share menu. For example, a messaging app that needs to receive messages even when closed would benefit from the TWA's ability to use native push services. Another case is when the app must appear in the Google Play Store with a native feel, as TWAs can be packaged as APKs. However, if the app only needs offline support, caching, and a home-screen icon, a PWA is simpler and cheaper. The choice depends on how much device access the app truly needs.
11. What is one possible future improvement for PWAs in Firefox?
One possible future improvement for PWAs in Firefox is adding support for installing PWAs as standalone desktop applications. Mozilla has been working on a feature called 'Progressive Web Apps for desktop' that would allow Firefox to launch a PWA in its own window, similar to Chrome and Edge. This feature is currently in development and may be tested in Firefox Nightly. Another improvement could be support for the Badging API and other advanced features. However, no release date is confirmed. The community is also requesting better push notification support. Mozilla is taking a careful approach to ensure privacy and security are maintained while adding these capabilities.
12. Name two other mobile browsers that support PWA installation.
Two other mobile browsers that support PWA installation are Opera and Brave. Opera on Android has a built-in VPN and ad blocker, and it allows you to install PWAs by tapping the menu and selecting 'Add to Home Screen'. Brave, which focuses on privacy, also supports PWA installation on Android with a similar process. Additionally, Microsoft Edge on Android supports PWA installation. Each browser may have slight differences in the installation prompt, but all use the same underlying web standards. Some lesser-known browsers like Vivaldi and Firefox Focus do not support PWA installation. It's always good to check the browser's capabilities if PWA support is important.