Can I rely on the Web Platform features to build my app?
An overview of the device integration HTML5 APIs
To create a native-like experience, Web applications have to meet the criteria of the intended PWA platforms and stores, including all splash screens, icon sizes and assets. According to a number of different sources, in order to cover all sizes and platforms, approximately 100 images might be needed.
Most of the Service Worker tutorials we can find on the Web focus on the initial development efforts needed to get the offline mode capabilities or performance gains for subsequent visits. But for production readiness, it is not enough, though. We need to have the update strategy in place not to cut off our users from actually getting the updates of our PWA.
Progressive Web Apps (PWA) is a modern way to build applications, including mobile ones, using purely web technologies and relying purely on the capabilities and strengths of the Web platform. Historically, it was the lack of these capabilities on the Web that caused the boom of the mobile apps, using so-called "native" (platform-specific) development approaches.
Google Chrome, as expected from the Service Worker API and whole Progressive Web Apps ideas main proponent, offers probably the richest developer tooling to ease the debugging, testing and experimenting with the APIs. Chrome's Dev Tools has a whole Application tab dedicated to PWA-related matters.
Progressive Web Apps are considered the next earthquake when considering mobile internet usage. But which company can benefit the most from introducing a PWA?
Article by e-point.com
Most of the browsers nowadays, including mobile browsers, allow the applications to retrieve and use the data stream coming directly from the user's device camera. But it's very common for the devices nowadays to have more than one camera available and we might have a preference which of these cameras is better suited for our app's needs. Fortunately, the Media Stream API has us covered.
One of the most complex and possibly annoying aspect of the offline mode implementation for Progressive Web Apps is when it needs to deal with cross-origin requests. As Service Worker is intercepting all the HTTP requests originating from our application, it means that also these reaching the external servers are to be handled, and this in turn means we need to deal with Cross-Origin Resource Sharing (CORS).
Analytics is the key non-functional feature our applications need to have nowadays. It's the hard numbers that should have the decisive voice whenever it must be chosen whether a feature, design or idea is worth exploring. With new Web APIs and the rise of the Progressive Web Applications, there are new aspects we should keep track of and possibly use as an axis of our analysis.
Geolocation API is definitely one of the best known device integration APIs we have on the web, both thanks its usefulness as well as its age. It lets the apps gain access to the user's location, expressed as geo-coordinates and subscribe to its changes. The possible usages range from location-based content filtering through mapping services to city games.
What makes a good Push Notification? Get tips to help you push value to your users and not users away.
Article by pwafire.org
Add support to tell the Web Browser to prompt the user with your native app install banner instead of the web app.
HTTPS is a crucial part of the user experience. It’s not just for really important or security-sensitive sites.
The number of people who access the internet with their mobile devices has increased and recent statistics show that mobile users consume twice as much content as desktop users.
Mobile is in pole-position as the go-to sales and marketing channel. According to Statista, 62% of global users access the internet by mobile phone. By 2020 the number of smartphone users is projected to reach 2.87 billion globally.
