Turn the home screen
into your next customer touchpoint.

01 A web page can live on the home screen

Think beyond PWAs as substitutes for native apps.

Web pages are usually reached through search, social media, or links, and the entry point disappears when the page is closed. OJapp places the page itself on the smartphone home screen, leaving a direct way back outside the browser.

1P1A does not mean forcing every page into an app. It means choosing pages worth keeping on the home screen and giving each one its own name, icon, and launch URL.

02 1S1A and 1P1A

Neither is inherently better. The difference is what you define as one app.

OJapp’s 1P1A script dynamically generates a Web App Manifest from the page URL, title, and icon candidates. It removes the need to maintain a separate static manifest.json for every page and enables page-level PWA design with one script line.

03 What OJapp PRO can do

Design what happens after a page reaches the home screen.

04 Add → Launch → Welcome

Use the moment users return instead of sending a notification.

The OJapp PRO journey is simple: users add the page to their home screen, launch it when they need it, and receive relevant information or a next step at that moment. PRO measures that intentional launch.

An offer can contain a short message, image, and link URL. The link can lead to an existing booking page, store, form, checkout, Notion page, or other service. OJapp connects the home screen to the tools you already use.

05 How to think about Analytics

See the relationship with the home screen that page views alone cannot show.

While general analytics covers traffic and browsing across the web, OJapp PRO focuses on the home screen as an entry point: whether the page was kept, whether users returned from it, and what they did afterward.

06 Home Screen Offer

A small welcome for people who kept your page on their home screen.

After appearing, the offer minimizes into a compact button and can be reopened when needed. Avoiding persistent interruption is part of designing an app users will keep.

07 Use cases

Pages with a reason to return are the best fit for the home screen.

OJapp PRO is not only for cases that call for daily notifications. It also fits pages that are not needed often but are valuable to open instantly when the time comes. The harder a page is to find again, the more useful its home screen entry point becomes.

08 Quick Start

Start by adding one issued line without rebuilding your existing site.

Setup is simple. After registration, configure your site to receive a site-specific JavaScript URL, then load it on the target site.

Note: oj_xxxxx.js is an example. Each registered site receives its own URL.

09 Page, site, and group settings

Add page-specific settings only when needed.

With 1P1A, add ojapp:title / ojapp:icon only when you want a page-specific app name or icon. If omitted, the Manifest is generated from the page’s existing information.

10 Manifest / Install Presentation

Add a dedicated description and visuals to the install screen.

You can separate the search description from the install description.ojapp:description takes priority in the Manifest; otherwise the regular meta description is used.

Specify one or multiple install-screen images for each page.

11 Conclusion

Do not let the web end when a page is closed.

The web is powerful because anyone can access a URL without an app store. 1P1A brings that page to the home screen, and OJapp PRO adds measurement and a launch experience to the entry point.