Based PWA (based on what?)

Article
Preston Brown

2 months ago by prestonbrown

I really liked @joshua’s Bitpost related blog about PWA’s. In fact, when working on Bitsurf, the team had a big discussion about building mobile-first, with PWA’s in mind. Our initial proof of concept that we worked on a for a few weeks was PWA compatible - the upcoming, more official, project is a PWA as well.

After watching the Parler debacle, as they were kicked from Apple, Google, and Amazon, we thought it is not worth the potential hit to get an app removed from a centralized distributor like the App Store. Investing all this time into a service that ultimately wants to tax a third of you revenue is to play into a con.

The biggest benefit is you can write software in a platform agnostic manner. A PWA is written 99% the same way on iOS and Android, as well as linux, and windows. Though some functionality is lacking, depending on the platform (like notifications on iOS), you have the insurance of retaining the work you’ve put in to building your app. A platfom can not just thanos snap your app on a whim.

PWA’s are not super popular, they have a different kind of install process, which induces friction to onboarding. They also are discouraged by a lot of the popular software platforms like Apple. Their lack of presence on the popular app stores doesn’t help with growth either.

I think a crypto product that is not heavily reliant on traditional payment methods does not have much to worry about outside of these concerns. Users are already kind of out on a fringe of some sort, and are more open to non-traditional product experiences. In fact, many are seeking out an atypical platform. The best thing PWA leveraged platforms can do is educate their users on the benefits and differences as opposed to a native app - normalizing PWAs more broadly.