User-friendly install practices from in app (embedded) browsers

Dear Gliders and experts, and especially Glide CEO,

Assuming that my app would get lots of visits from social apps (facebook, instagram etc) and their embedded browsers wouldn’t let my potential blondie users save glide app to their mobile home screens…

…What are “the best practices” and most user-friendly ways that you came to?

I have searched through the community forum and read half a thousand posts in almost hundred topics where people asked quite the same in different words - and I didn’t find any good answers except for user guidance/instructions or sending complains to vendors :slight_smile:

So, is there a way in Glideapps and how to:

  1. Detect that my app was loaded in an embedded browser (to initiate “install guidance”)?

  2. Provide a link or script (for a button or img or reach/action text) that would do or suggest/offer a user open it in native browser (safari/chrome)?

  3. Detect that app was loaded in native browser (safari/chrome) to force or at least show guidance/instructions for user to Add app to home screen (through visibility or other condition) apart from those provided in browser itself

  4. Detect that app was loaded as a PWA from home screen (to avoid all those guiding steps and show core app functionality)?

That’s the scenario a came to after all readings, but if you have realized any better please respond here

And, with all respest to the community and creators, please propose instead of wasting time with this “I am afraid the PWA install mechanic can’t be changed by Glide, as it is device / OS specific” :slight_smile:

Thank you!


sample for action on point 2

1 Like

@david hello and apologies for disturbing, can I draw your attention to this topic here please

1 Like