Google moves Instant Apps closer to reality

Ryan Daws is a senior editor at TechForge Media, with a seasoned background spanning over a decade in tech journalism. His expertise lies in identifying the latest technological trends, dissecting complex topics, and weaving compelling narratives around the most cutting-edge developments. His articles and interviews with leading industry figures have gained him recognition as a key influencer by organisations such as Onalytica. Publications under his stewardship have since gained recognition from leading analyst houses like Forrester for their performance. Find him on X (@gadget_ry) or Mastodon (@gadgetry@techhub.social)


Google is furthering its vision to make Instant Apps, well, instant, with an update to its programming kit.

The issue with today’s instant Android apps is that Google has to load support for every possible device. With the number of Android devices available globally, many with very unique configurations, this can slow down the loading of the apps considerably.

Developers can now target specific device configurations with unique profiles. A device with a low-resolution screen, ARM chip, and German language, for example, will not have high-res assets, support for an Intel chip, and other languages delivered to it.

On average, Google believes this saves around 10 percent space and will translate to faster loading. This may not sound very much, but every second or so saved helps to get closer to Google’s vision for Instant Apps and gets users into your pride and joy quicker.

Better still, whereas previously a user required Android Orea to preserve data in their Instant App session, this is now available to all devices running Lollipop or newer.

Enabling all of this new functionality will require some manual work on your end. Find out more about how to enable it on Google’s official blog post here.

Do you plan on supporting the new Instant Apps functionality? Let us know in the comments.

View Comments
Leave a comment

Leave a Reply

Your email address will not be published. Required fields are marked *