alt Hacker NewsHere's what I would do.
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!
Replies
If somebody wouldn't even bother to download an app for a social network they probably wouldn't stick around for very long either
After a quick search, there is an NFC web API, but with no general support https://developer.mozilla.org/en-US/docs/Web/API/Web_NFC_API
That’s empirically wrong. All statistics say that people do install apps way more than PWA
> 1. Make it QR code scanning instead of tapping so it can be a PWA.
Misses the point completely. The entire idea is that this enforces in-person meetings, which QR codes do not.
> 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.