User Resistence: App Store vs PWA

This is just a general Community question… Does anybody else experience user resistance because glide apps aren’t “real” apps? I think real apps means you can get them from the App Store.

This seems to be a point of friction for getting people to adopt our app, and I’m wondering if anyone else has experienced it and if you have any strategies to overcome it.

I think it depends who your target audience is.

If your app is a B2C public-facing app – which Glide isn’t meant for – then I can imagine that you will not get the adoption you are hoping for (because you’re not distributing your app in the usual channel) and you won’t offer the same bells and whistles of a custom-made B2C app.

If however your app is a B2B internal business app – which Glide is meant for – then in my experience people are thrilled to be able to improve a process or have access to information that would otherwise be a cumbersome, unpleasant or inefficient experience (pen & paper, Excel, not possible until at a desk, carrying around a catalog, etc.).


@nathanaelb has it right.

While anyone can use Glide to build apps without code, Glide is developed with business tools in mind, and those usually aren’t provisioned from the app store because they’re internal/private.

That said, we have seen non-business apps do surprisingly well.

It usually depends on how the app creator presents/distributes the app to their audience.

@Rich_Dixon - How are you distributing your app today? What friction are you encountering? What are your users saying?

1 Like

We have a donor who matches $1 per mile for people who bike, or run. The money goes to a home that serves kids rescue from human trafficking. My app is simply a way for people to enter their miles and create a community where everyone can see how many people are involved.

It works really well for the people who get into the app, but a number of people have trouble with the whole pin/sign in process and they just give up. Or they decide that this isn’t a real app and they don’t even try.


What I’ve seen work for others:

  • Use a proper name for the app
  • Use a custom domain like or
  • Have a page on their site promoting the app & showing how to install it

Put together this all makes the app look & feel more legitimate.

So, in your case, maybe something like:

  • Rename the app from Beta HF to Hope & Freedom Challenge
  • Use the custom domain or something similar
  • Add a page to the site talking about the app’s features and how to use it

Hope that helps (no pun intended). :slight_smile:


@NoCodeAndy This makes sense. I’m gonna have to decide if there’s a better presentation and if the frction is worth the cost savings.


1 Like

@Rich_Dixon I would add to this list:

  • Enable Google Sign In. Not all of your users will be able to take advantage of it, but those that can will get a much more seamless experience.

When I describe my apps, I use the fact that they are not on the App store as a benefit - they are custom apps targeting very niche/specific/geographic/etc audiences and are not meant for 5 million users. Bespoke, so to speak :wink:

Just position it differently.

I also describe Glide as a data-driven hybrid, somewhere between an app and a website, and more powerful and agile to easily customize to the owner/client needs.


@kabookie This makes a lot of sense. It’ll be helpful as we grow our little group. Thanks.

1 Like

Thanks @Darren_Murphy. I need to learn about Google Sign In.

Absolutely agree with this.
If a client is asking for their App to be made available via the App stores, I generally take that as a warning sign that Glide might not be the correct choice for their App.