Progressive web apps explained: app-like websites without the app stores

A progressive web app, or PWA, is a website built so it can behave like an app. People open it in the browser like any site, but they can also add it to their home screen, open it in its own window without the browser bar, get fast loading on repeat visits and, if it is designed for it, keep using parts of it on a weak or missing connection. There is no app store download, and updates reach everyone as soon as you publish them.

What makes a website a PWA

Three technical pieces turn an ordinary website into a PWA:

• HTTPS. The site must load securely. The other pieces depend on it.
• A web app manifest. A small file that tells the phone the app's name, icon and colours, and how it should open when launched from the home screen.
• A service worker. A script that runs in the background of the browser. It can store files and data on the device so pages load fast and work offline, and it can handle notifications if the user allows them.

On top of these, a good PWA is designed mobile-first, works on any screen size and stays quick on modest phones.

What a PWA can and cannot do

Strengths

• One codebase serves Android phones, iPhones and computers.
• No app store approval for each update.
• Usually lighter on storage than a full native app.
• Its pages can still be found through Google, unlike content locked inside an app.
• It can keep working through brief signal drops, if offline use is designed in.

Limits

• Support differs between browsers and phones. Some features, such as install prompts and notifications, behave differently on iPhone and Android, and they change over time. Test on the devices your customers actually use.
• Deep access to some phone hardware and background tasks is more limited than in a native app.
• Without an app store listing, people may not think to look for it; you have to show them how to add it.
• Offline features need careful design, especially for data that changes, such as stock levels or prices.

PWA, website or native app?

If you are still deciding what kind of product you need at all, start with website, web app or mobile app.

Where a PWA fits well in Bangladesh

Many people use mid-range Android phones with limited storage and watch their mobile data closely, and many businesses operate in district towns or rural areas where the signal comes and goes. That makes a PWA a practical option for:

• Field sales teams taking orders from shops. For example, a hypothetical feed company's sales officers in Dinajpur could record orders offline and sync them when the signal returns.
• Repeat customers who order regularly and would value a home-screen icon without a large download.
• Staff tools for stock checks, attendance or delivery updates across branches, where installing a store app on every phone is a hassle. For branch stock, see one inventory and POS system across branches.
• Content sites that want fast repeat visits on slow connections.

A PWA will not fix a slow site by itself. If the underlying pages are heavy, start with making the website fast on mobile data.

Common questions

Can a PWA be listed in app stores? Some can be packaged for app stores, but that is a separate step with each store's own rules. Check the store's current requirements.

Does it replace my website? Often it is your website, improved. The same pages serve visitors from Google and people who installed it.

Is it cheaper than a native app? Usually you build one product instead of two, but offline features and testing across devices still take real work.

Before you start

1. List what users must do and what must work offline.
2. Decide which devices and browsers matter most.
3. Plan how users will learn to install it.
4. Test on low-cost phones with weak signal, not only on office Wi-Fi.

If a PWA sounds like a fit, my web development service page explains how I approach projects like this.