Can one domain provide multiple PWAs? This guide explains id, start_url, and scope, then explores 1S1A, 1G1A, 1P1A, and UDA: a model where users can define the final home screen entry through URL state.
Using start_url:"/" is perfectly valid for a site-wide PWA, but it can conflict with what users expect when they add a specific page to their home screen. Here is why the choice of launch URL deserves more thought.
Which websites are a good fit for PWA? Blogs, e-commerce, web tools, membership services, and local business sites can all benefit in different ways. The key question is simpler: does the user have a reason to return to the same URL?
A local business PWA does not have to be a full custom app. Restaurants, salons, clinics, and shops can use the home screen as a direct return path to reservations, menus, opening hours, coupons, and other pages customers use repeatedly.
Membership sites are built for repeat visits. A PWA can give users a direct home screen entry to dashboards, reservations, lessons, or account pages instead of making them start from the public homepage every time.
A useful web tool should not require a search every time you need it. Turning a frequently used web tool into a PWA can give it a direct home screen entry, making timers, calculators, generators, converters, and other lightweight tools feel much closer to everyday apps.
PWA for e-commerce does not have to mean turning the entire store into one app. Individual product pages can become home screen entries, giving shoppers a direct way to return to products they are considering, waiting for, or buying repeatedly.
Turning a blog into a PWA is not just about making it look like an app. The bigger opportunity is giving readers a direct home screen entry to your blog or a favorite article, creating a simple path for future return visits without relying on search or social media.
What does the id field in a Web App Manifest actually do? Learn how browsers identify PWAs, why start_url becomes the identifier when id is omitted, and how id affects multiple PWA installations and page-level app design.
How much of a PWA can you build with a Web App Manifest and no Service Worker? Based on 2026 Chrome behavior and real-device testing, this article covers installation, icons, standalone display, start_url, and what still requires a Service Worker.
OJapp Tips is a technical blog documenting real-world PWA behavior, iPhone Safari quirks, home screen installation, manifest.json, Service Worker, Web App Manifest, WebClip, icon cache issues, and practical web development tips based on actual testing with iPhone, Android, and PC.
The articles are based on hands-on experiments from PWA LAB and real development experience with OJapp, Petal, and OJ-Pass. Instead of only repeating official documentation, OJapp Tips focuses on the details developers actually get stuck on.