1. Make it QR code scanning instead of tapping so it can be a PWA.
2. Make it a PWA. This will make it accessible to many more people. Nobody wants to install an app. Nobody wants to install a PWA either but they will at least use a "web site" (a surprising number will install it if it's good).
3. Save yourself a lot of money by building it on top of the Nostr protocol. Run a relay yourself if you want guaranteed reliability. Run a Blossom server for media. Use email for auth and store people's keys for them if you want a traditional UX. Don't worry about what's on Nostr already, just build your own thing on the protocol.
Let people come and go as they please and don't lock them in. They will love you for it later.
> Make it a PWA. This will make it accessible to many more people. Nobody wants to install an app. Nobody wants to install a PWA either but they will at least use a "web site" (a surprising number will install it if it's good).
I’ve worked on a platform for social media apps. When the social network had a native iOS app, a native Android app, and a PWA, users chose iOS about two thirds of the time, Android about a quarter of the time, and PWA about 10% of the time. That’s across all users, including desktop, so the PWA actually had an unfair advantage.
People strongly prefer native apps to PWAs, especially for social media.
Such a conclusion cannot reasonably be made from the data you have presented. It merely means that your web app was not preferred over your native app.
But people are used to that now being the normal state of things, it's rare that they even try the browser -- I develop an application that is web only and typically used on desktops, and people incessantly ask me for "an app so they can use it on their phone".
They probably want an icon to open your app. They probably dont know the difference between an app rendered with a browser or a truly native app. In the past apple as made it difficult for users to know how to do this and users just know about the app store. Great for apple (walled garden) and social media apps (more tracking, unlimited ads) but not great for users.
Yes, that's the "workaround" I use but by default people are expecting to find something in the app store.
> They probably dont know the difference between an app rendered with a browser or a truly native app.
Absolutely, users do not know or care what technology you are using so long as it meets their expectations of use. Users are going to the app store as a discovery mechanism for "something that gives them an icon on the phone to get to that thing", most have no clue what "native code" means.
Yes, of course some people will feel that way, but also having less friction is not always necessarily a good thing because it requires less of a time investment for the user to get started, so therefore they are actually more likely to just churn. It is a balance
Granted, there's a lot of crap apps out there. But properly built apps are a world apart from your typical PWA's or web sites (or even really good ones)
We’re not normies, so take that with a grain of salt. Here’s mine: apps have access to significantly expanded capabilities which has privacy implications. If I can use the browser for a given app, I do it. Amazon for example.
As a native app writer, this has been my experience.
Mentioning it here, though, tends to get pushback from folks that write Web apps. They don’t want to admit that native apps have more capabilities than Web apps; even if that’s a bad thing, because of security risks.
People say PWAs are good as apps now and feels like an app now, personally as ab armchair nobody I doubt the retention rate actually compare, even if the app was literally just a plain WebView.
Personally I'll only install FOSS apps on my phone and I go out of my way to actively discourage (to varying degrees of success) my relatives from installing arbitrary junk that they surely don't need on their phones.
If one is going through the hassle of joining a video call on a different device to then scan it with their smartphone, all to just connect with another person, you could reasonably assume that they're friends.
Maybe if there's a "celebrity" that displays it on a live stream, that's a bigger issue, but there could be other mechanisms to dissuade this behaviour. Perhaps you could only add one friend with one QR code.
1. Make it QR code scanning instead of tapping so it can be a PWA.
2. Make it a PWA. This will make it accessible to many more people. Nobody wants to install an app. Nobody wants to install a PWA either but they will at least use a "web site" (a surprising number will install it if it's good).
3. Save yourself a lot of money by building it on top of the Nostr protocol. Run a relay yourself if you want guaranteed reliability. Run a Blossom server for media. Use email for auth and store people's keys for them if you want a traditional UX. Don't worry about what's on Nostr already, just build your own thing on the protocol.
Let people come and go as they please and don't lock them in. They will love you for it later.
Cool project. Have fun!