The future of web development
Be one of the first few in Charlotte County to upgrade your digital business to the 21st century. Bring the power of PWA and AMP to your website.
A progressive web application takes advantage of the latest technologies to combine the best of web and mobile apps. Think of it as a website built using web technologies but that acts and feels like an app. Recent advancements in the browser and in the availability of service workers and in the Cache and Push APIs have enabled web developers to allow users to install web apps to their home screen, receive push notifications and even work offline.
AMP is a simple and robust format to ensure your website is fast, user-first, and makes money. AMP provides long-term success for your web strategy with distribution across popular platforms and reduced operating and development costs.
Progressive Web Apps and AMP pages work great together. In fact, in many cases, they complement each other in one way or another. Learn how to:
- Enable PWA features for your AMP pages
- Create a compelling, super-fast user journey
- Simplify your app by using the power of AMP
AMP pages with app features
AMP Pages can use many app features on their own, as long as they’re served from your origin (your site’s domain) as opposed to an AMP Cache. This means that app features won’t kick in when consuming an AMP Page within a platform like Google or Bing, but they will on the onward journey, or if users navigate to your AMP pages directly.
AMP as an entry point into your app
AMP’s unique selling point is the almost-instant delivery, a characteristic that makes AMP the perfect fit for the first user interaction with your site. Progressive web apps enable much more interactivity and engagement-enabling features, but their first load is hindered by the fact that the site’s Service Worker, and therefore its assets and app shell, are only accelerating delivery on subsequent loads.
How does it work
A Progressive Web Apps is a web app (not a hybrid app, or at least not in the way most of us know them) with improved functionality. Users can “install” progressive web apps with minimal fuss right from the mobile browser—are simply web pages that get pinned to the home screen.
The difference is that progressive web apps provide a more native app-like experience for users than web apps or web clips. Progressive Web Apps can specify properties such as their icon, name, and splash screen, and can send push notifications.
Progressive Web Apps also boasts offline usability, thanks to browser support for service workers. Now, functionality will depend on how much an individual app requires an internet connection for its core features, but that’s the same with any app. This could mean basic app functionality remains even if you lack access to the internet, such as access to cached assets and articles.
There is one downside to progressive web apps not going through any app store: no quality control. However, that doesn’t mean PWAs are completely insecure. Developers have to register service workers over HTTPS, and Progressive Web Apps still don’t have nearly as much access to the OS as native apps.
The PWA experience on iOS
Apple finally (and quietly) included support for service workers in iOS 11.3. Progressive web apps get support in-app switcher, where you see the actual app name and not just “Safari” like with web clips.
However, there are some caveats to service worker support in iOS. The big two are that Apple does not support push notifications or background sync. Progressive Web Apps do have Apple Pay support (since Apple Pay works on the web), but not In-App Payments. They also cannot access Bluetooth, Touch ID or Face ID, Siri, or private information.
Unlike Android, installation is more of a manual process. There’s no suggestion web banner, instead, users have to select the Share button and then the Add to Home Screen button. This reduces the chance of app discovery on iOS, especially if the user is unaware there is a Progressive Web App available.