Make Layerise Product assistant part of your existing Andriod app

settings ·

If you have an existing mobile application for customers and want to provide an effortless yet effective post-sales experience in the same application, Layerise Application can be embedded into your existing application to combine your existing business applications and post-sales experience.

Why?

That is a good question. You might consider the following points:

  • With this practice, you save hassle for customers to check 2 different platforms every time they have queries or challenges with the product.
  • You may want to add a layerise product assistant to an existing iOS/Android app to have resources (you created in Layerise product assistant) on the same platform.
  • New features/fixes can be shipped faster because you don't have to go through the publishing process every time you make a change in Layerie product assistant components.
  • The app will still be available at the App/Play Store, so users can find and install it over different channels

How does it work?

Layerise Product Assistant will be displayed inside a Trusted Web Activity. Bubblewrap is a set of libraries and a command-line tool (CLI) for Node.js that helps developers generate, build and run Progressive Web Apps (Layerise product assistant) inside Android applications, using Trusted Web Activity. The technology leverages the browser to render the PWA in full screen, ensuring the Trusted Web Activity has the same compatibility with the Web Platform features and APIs that the underlying browser does. There are also open-source utilities to make implementing an Android app using a Trusted Web Activity even easier.

PreRequisites

Layerise product assistant in a Trusted Web Activity must meet the PWA installability criteria.

Additionally, to match the behaviour users expect from Android applications, Chrome 86 introduced a change where failing to handle the following scenarios is considered a crash:

  • Failure to verify digital asset links at application launch.
  • Failure to return HTTP 200 for an offline network resource request.
  • A navigation request returning an HTTP 404 or 5xx error".
  • When one of those scenarios happens in the Trusted Web Activity, it causes
  • A user-visible crash of the Android application. Check out the guidance on handling those scenarios in your service worker.

You can read all about Trusted Web Activity here

If you want to do it from scratch (or have never done this before), refer to this official google demo link:

https://github.com/GoogleChrome/android-browser-helper/tree/main/demos

Have a question?

Ervin
Oscar
Martina
Emil
+9

Trusted by companies like

RaleighJägermeisterDrinkmateWellis

Copyright © 2022 Layerise ApS. Made with 🧁  in Denmark · LinkedIn