Progressive Web Apps for Indonesian Businesses: A Practical Guide

One Friday night, a coffee shop owner in Bandar Lampung opened a food delivery app and found his shop ranking high with plenty of reviews. He smiled. Then he opened his own website on a customer's phone—and the smile turned into a frown. The site was slow, required reloading every time it was opened, and looked like it was built in 2015. One question formed in his mind: why should customers bother downloading an app to order, when they could just do it from the browser?

That question actually has had an answer for several years now. It's called a Progressive Web App, or PWA.

What Is a Progressive Web App (PWA)?

A Progressive Web App is a website that behaves like a native application. It opens in the browser, but it can be installed to the home screen, work offline, receive push notifications, and load almost instantly. Users don't need to download anything from the App Store or Google Play. They just visit a URL, and the system offers to "Add to Home Screen."

Think of it as the best of both worlds: the easy access of a website with no installation process, plus native-app capabilities like notifications and offline mode. That's a PWA.

This technology isn't new. Google popularized the term around 2015, and it has since been widely adopted by global companies. Twitter (now X), Pinterest, Starbucks, Alibaba, and many others built PWAs to reach users who don't want the hassle of installing an app.

Why PWA Matters for Businesses in Indonesia

Indonesia has one of the most active internet user markets in the world. Data from APJII (the Indonesian Internet Service Providers Association) shows internet penetration has surpassed 79 percent since 2024, with the majority of access happening through mobile phones. DataReportal records Indonesian internet users spending an average of more than 7 hours online per day.

But there's an irony behind those numbers. Internet connections in Indonesia aren't always stable, especially outside major cities. Data quotas are still a consideration. And users' phone storage is often full of apps they rarely open.

This is where PWA shines:

• Accessible without installation. No need to convince customers to download a new app. Just one link.
• Works offline or on weak connections. Content that's already loaded remains accessible without internet.
• Lightweight. Doesn't consume much storage space or data quota.
• Always up to date. Users don't need to update through an app store; the latest version loads automatically.

For businesses in Indonesia, with a mobile-first market and connections that are sometimes unstable, this combination is very attractive.

PWA vs Native Apps: An Honest Comparison

Before deciding, let's compare PWA with native apps honestly. Each has its own strengths and weaknesses.

The conclusion: for most businesses that need a mobile presence—catalogs, ordering, information, customer accounts—PWA is often sufficient and far more economical. Native apps become necessary when you need deep hardware access (like delivery apps with intensive real-time GPS tracking), features requiring very deep OS integration, or a presence in app stores that is genuinely strategic.

Measurable Benefits of PWA

1. Higher Conversion and Engagement

Data from various studies shows PWAs increase engagement. For example, when Pinterest moved to a PWA, they reported a 40 percent increase in time spent, a 44 percent increase in ad clicks, and ad revenue up 52 percent. Starbucks reported a 23 percent increase in daily orders after switching to a PWA.

These numbers aren't a guarantee that every business will get the same results. But the pattern is consistent: PWAs remove friction between users and the desired action.

2. Faster Loading

Speed is a proven conversion factor. Google found that the likelihood of users leaving a site increases by 32 percent when load time goes from 1 second to 3 seconds. PWAs are designed to load fast, even on slow networks, because service worker caching strategies allow content to load from the user's device instead of the server.

3. Reaching More Users

Not everyone is willing to download an app. Global data shows the majority of phone users don't install new apps every month. PWAs reach those who avoid installing, including users with low-end phones and limited storage—a very large segment in Indonesia.

4. Lower Cost

This might be the most practical reason. Building one PWA is much cheaper than building two native apps (Android and iOS). For businesses with limited budgets, the difference can mean building or not building at all.

When Should You Choose a PWA?

Not every case needs a PWA. There are situations where PWA is the best choice, and others where a different path is better.

PWA is the right choice when:

• You need a mobile presence with a limited budget. One codebase for all platforms saves millions of rupiah.
• Your content matters more than hardware features. Product catalogs, news, service information, ordering, user accounts—these all work great as PWAs.
• You want to start fast and gauge interest. PWAs can launch much faster than native apps, letting you test the market before a big investment.
• Your target audience is mobile-first. The majority of Indonesian internet users access via phones. PWAs deliver a smooth mobile experience without installation barriers.

Native apps are better when:

• You need intensive hardware access. Continuous GPS tracking, complex camera processing, specialized sensors.
• App store presence is the strategy. Some businesses genuinely depend on visibility in the Play Store or App Store.
• You need maximum performance for heavy tasks. Games, video editing apps, apps with complex graphics.

How PWAs Work: The Technology Behind Them

PWAs are built on three main pillars:

1. Service Worker

A service worker is a JavaScript script that runs in the background of the browser, separate from the web page. It manages caching, handles network requests, and enables offline mode. When a user visits the website for the first time, the service worker records assets that need to be stored. Subsequent visits can be served from the cache, even without an internet connection.

2. Web App Manifest

The manifest is a JSON file that defines how the app looks when installed: name, icons, theme color, screen orientation, and more. This is what makes the browser offer the "Add to Home Screen" option.

3. HTTPS

PWAs only work on secure websites (HTTPS). This isn't just a technical requirement; it's also a security guarantee: data sent between user and server is encrypted. Fortunately, SSL certificates can now be obtained for free from Let's Encrypt or are provided automatically by modern hosting services.

Beyond these three pillars, modern PWAs also leverage various browser APIs for extra features: push notifications, background sync, local storage, and more.

Steps to Building a PWA

If you've decided PWA is the right path, here are the realistic stages:

1. Define Goals and Core Features

A good PWA starts with clear goals. What should users be able to do? Do they just read information, or do they need to create accounts, order, or pay? Start with core features, not a complete list that only 1 percent of users will ever touch.

2. Evaluate Your Existing Website or App

Do you already have a website that could become a PWA? Many modern frontend technologies (like Next.js) have built-in PWA support. Upgrading an existing site is often much cheaper than building from scratch.

3. Prepare the Infrastructure

Make sure your site already uses HTTPS. Set up fast, reliable hosting. Measure current performance as a baseline before optimization.

4. Technical Implementation

This includes building the service worker, manifest, caching strategies, and performance optimization. For an experienced team, this stage typically takes 2–6 weeks for a simple to medium PWA.

5. Test on Multiple Devices

PWAs must be tested across browsers (Chrome, Safari, Firefox) and phone classes—from flagship devices to budget phones with limited RAM. Offline behavior also needs thorough testing.

6. Launch and Measure

Launch, then measure: how many users install the PWA to their home screen, how long sessions last, what the conversion rate is. This data determines the next optimization steps.

How Much Does Building a PWA Cost in Indonesia?

PWA costs vary widely depending on complexity. Here are realistic ranges for the Indonesian market:

Compare that with native apps: building Android and iOS apps separately generally costs two to three times more than a PWA, plus the cost of maintaining two different codebases.

Mistakes to Avoid

1. Treating PWA as a "Cheap App"

A PWA is not a budget version of a native app. It's a different architecture with its own strengths and limitations. Teams building PWAs need to understand service workers, caching strategies, and the differing behavior of browsers.

2. Ignoring Safari

Many PWAs are only tested in Chrome. Yet most iOS users browse with Safari, and Safari's PWA support differs from Chrome's. Some features (like push notifications on iOS) were only supported later, and behavior can differ. Make sure your PWA is also tested and optimized for Safari.

3. Overly Aggressive Caching

A service worker that caches too much can serve stale content and make updates difficult. Caching strategies must match content types: frequently changing pages shouldn't be cached too long; static assets can be cached aggressively.

4. Forgetting SEO

A PWA is a website, and websites need SEO. Make sure URL structure, meta tags, structured data, and content remain search-engine friendly. Some PWA approaches that rely too heavily on JavaScript can confuse Google if not implemented properly.

PWA for Different Business Types

SMEs and Local Shops

For SMEs, a PWA can be an affordable and effective mobile presence. Product catalogs, opening hours, clickable WhatsApp buttons, and offline mode for viewing the catalog without internet. This turns an ordinary company profile site into a tool customers actually use.

E-commerce

PWA is a popular choice for online stores because it removes installation friction. Customers can browse, order, and pay directly from the browser. Offline mode lets them view the catalog when the connection drops. Push notifications can remind them about promos or order status.

Restaurants and Cafes

Digital menus, online ordering, and queue systems can be built as PWAs. Customers scan a QR code, open the menu, and order without installing anything.

Services

Booking, portfolios, forms, and customer account systems all work very well as PWAs. Clients can access information and make reservations with minimal friction.

Companies with Internal Apps

PWAs are also popular for internal company apps (HR, attendance, reporting) because employees don't need to install special software. Open in a browser, done. This eliminates many device management headaches.

Integration with Existing Systems

A PWA doesn't have to stand alone. It can integrate with systems you already run:

• Payment gateways — integration with midtrans, Xendit, or other payment providers for transactions.
• CRM — syncing customer data and interaction history.
• ERP — a PWA can be the mobile frontend of a company's ERP system. This relates to our guide on when to move to ERP.
• POS systems — a PWA can be the mobile interface of a point-of-sale system.
• Notifications — push notification integration for reminders, status updates, or promos.

Measuring PWA Success

After launching your PWA, measure the right things. Don't just look at traffic. Focus on:

• Installations — how many users add the PWA to their home screen.
• Engagement — session time, pages per session, visit frequency.
• Conversion — what percentage of visitors take the desired action (order, sign up, buy).
• Performance — load times, stability, offline behavior.
• Retention — do users come back after the first visit?

Compare this data with the pre-PWA baseline to see the real impact.

The Future of PWA

The development direction for PWA remains positive. Browser support is maturing. Features that used to belong only to native apps—push notifications, camera access, geolocation, even payment integration—are increasingly available on the web. Apple, which was slow to support PWAs, continues to improve its support in iOS.

On the other hand, native apps still have their place for specific use cases. The decision isn't "which is better," but "which is more appropriate for your needs."

For most businesses that want a mobile presence at a reasonable cost, PWA is a very sensible choice.

Frequently Asked Questions

"Can a PWA be found on Google Play or the App Store?"

A pure PWA isn't listed in app stores. However, since 2023 Google Play has supported Trusted Web Activity (TWA), which allows a PWA to be wrapped in an Android app and listed on the Play Store. Apple's App Store still restricts PWAs, though iPhone users can add a PWA to their home screen via Safari. If app store presence is a strategic requirement, discuss TWA or hybrid app options with your technical team.

"Can a PWA accept payments?"

Yes. PWAs can integrate with any payment gateway that provides web APIs: Midtrans, Xendit, DOKU, and others. The Web Payments API also supports Google Pay and Apple Pay on compatible devices. For Indonesian businesses, integration with e-wallets and virtual accounts generally works smoothly in a PWA.

"Is a PWA secure?"

PWAs only run on HTTPS, which means data is encrypted. Service workers have strict security boundaries. But like all web applications, security depends on correct development practices: input validation, API protection, secure session management. A PWA isn't automatically secure—it's secure if built properly. Read our website security guide for businesses for the fundamentals.

"How long will a PWA last? Will it become obsolete?"

PWA is an open web standard supported by all major browsers and continuously developed by the W3C and browser vendors. Unlike proprietary frameworks that can be abandoned by their vendors, investing in a PWA is investing in the web itself. Good architecture—separating frontend and content, for example with a headless CMS—makes PWAs easy to update without rebuilding.

"Are PWAs suitable for internal company apps?"

Very suitable. Internal applications such as attendance and HRIS systems, reporting, or task management are often more effective as PWAs: employees don't need to install special apps on personal or company devices, updates are automatic, and they work from any device with a browser. This removes the device-management burden that often plagues mid-sized companies.

Next Steps

If you're considering a PWA, start with three things:

1. Audit your needs. What do users want to accomplish on their phones? What's holding them back right now?
2. Measure your current site. How fast is it? How mobile-friendly? This is the baseline for measuring PWA impact.
3. Consult with an experienced team. A hastily built PWA can be worse than a well-optimized regular website. An experienced team knows the right caching strategies, browser differences, and how to optimize for conversion.

The Kartech. team in Bandar Lampung can help you determine whether a PWA is the right path—and if so, build it properly. We don't sell packages; we start from your business problem. Start from the contact page or explore our services.

Also read: our guide to mobile app development services, the website cost guide, and how to choose a software house.