How to Update a Website-Based Android App

One of the most frustrating aspects of traditional native app development is the update process.

If you hire a developer to build an app from scratch, every single time you want to change a button color, fix a typo, or add a new screen, the developer has to write new code. They then have to compile a new version of the app, submit it to the Google Play Store, wait days for Google to review it, and then hope that the users actually download the update to their phones.

If you use an automated converter, this painful process is almost entirely eliminated. Here is everything you need to know about how to update a website-based Android app.

The Magic of the WebView

To understand how updates work, you must remember that your app is built around a WebView.

A WebView is an embedded browser. The app itself is essentially an empty shell that is programmed to point at your website URL. When the user opens the app, the WebView fetches the live version of your website from your server.

Because of this architecture, there are two distinct types of updates: Content Updates and Core Updates.

1. Content Updates (No App Store Update Required!)

99% of the updates you make to your business will be Content Updates.

A content update is anything that changes on your website. This includes:

• Publishing a new blog post.
• Changing the price of a product in your WooCommerce/Shopify store.
• Changing your website’s theme colors via CSS.
• Adding a new page to your navigation menu.
• Fixing a typo.

How to execute a Content Update:

You do absolutely nothing to the Android app.

You simply log into your website (e.g., your WordPress dashboard) and make the change there. The very next time a user opens your Android app, the WebView will fetch the newly updated website. The change happens instantly for all users across the globe, without them ever having to visit the Google Play Store to download an update.

2. Core Updates (App Store Update Required)

A Core Update is an update to the actual native Android "shell" that holds your WebView. You only need to perform a Core Update if you are changing the fundamental identity or native features of the app itself.

Examples of a Core Update include:

• Changing the App Icon: (The logo on the user's home screen).
• Changing the App Name.
• Adding Push Notifications: (If you didn't enable them when you first created the app).
• Changing the Splash Screen: (The loading screen before your website appears).

How to execute a Core Update:

If you need to change one of these core native features, you cannot just change it on your website. You must:

1. Return to the online website-to-app converter platform.
2. Enter your URL and upload your new App Icon or new App Name.
3. Generate a brand new .aab file.
4. Log into your Google Play Developer Console.
5. Upload the new .aab file as a "New Release."
6. Wait for Google to approve the update. Once approved, users will be prompted to download the new version from the Play Store.

Conclusion

The ability to bypass the Google Play Store update process for content changes is the single biggest advantage of a website-based Android app. By managing your app directly from your website's backend, you save massive amounts of time and money while ensuring your users always see the most up-to-date version of your business.