Web App vs Native App, Bypassing the Gatekeepers
Navigating the Complex Landscape of Mobile App Ecosystems and Embracing Web3 Innovations
Most smartphone users access the web through their devices and have dozens of apps installed, each dedicated to a specific brand.
But have you noticed something peculiar?
You launch the Kindle app from Amazon to browse books, pick a new novel, and are ready to buy—but there is no buy button. Or you spend time inside the OpenSea app looking for that new shiny NFT, yet again, where is the buy button?
In both examples, and many others, you must go directly to the Amazon or OpenSea websites to make a purchase. You can't buy from within the app. Why is that? And why doesn't the app even tell you to visit their website?
Meet the Gatekeepers
Apple and Google control over 99% of the mobile ecosystem, imposing strict restrictions on what goes through their app stores.
If you publish an app that sells something non-physical, you must pay them a cut of up to 30% of the price you charge. This fee is known as the "Apple Tax" and the "Google Tax."
Moreover, Apple and Google impose numerous restrictions on what can and cannot be done with cryptocurrencies and NFTs, making it nearly impossible to implement Web3 functionality within native apps. These limitations hinder the full potential of decentralized technologies and restrict the seamless integration of blockchain-based assets.
To avoid paying this substantial tax and navigating these restrictions, many businesses only allow purchases directly from their websites. However, Apple and Google do not allow these businesses to inform users about this restriction within the app. You have to figure it out on your own.
Web Apps
A Web App is similar to a Native App but runs inside your web browser, like Safari or Chrome. It offers fewer functionalities but, because it's on the web, it's not subject to Apple and Google's rules and taxes. Some Web Apps can even be installed directly from the browser, like a Native App, and are called Progressive Web Apps.
Why the SmartNFT Protocol (SNP) Uses Web Apps
The main purpose of the SmartNFT Protocol is to allow users to create, share, buy, and sell SmartNFTs in an interoperable and open way. No one wants to pay a 30% tax to buy a $10 coupon from someone else. SNP must operate outside the confines Apple and Google have constructed within our smartphones.
Practical Example from Smart Media Technologies
1. Scan the QR Code or use the direct link: Smart Wallet Demo.
2. The Web App loads in your browser.
3. Register.
You are now using a Web App built on the SmartNFT Protocol, leveraging the $VEE token. Associated with your new account is a Web3 Wallet managed directly by the SNP.
You don’t know about $VEE? » $VEE Token in a Nutshell
Brand Custom Wallet
The Web App and the underlying Wallet are Open Source technologies that are part of the SmartNFT Protocol. Each brand can create its own branded Web App for its specific use case.
Jameson Web App
The famous whisky brand launched a new marketing campaign built on the SmartNFT Protocol and has its own Web App: Jameson Whiskey.
It's very well done. I suggest you try it out, even if you don't plan to participate, just to use the Web App and get a sense of how brands will leverage the SmartNFT Protocol.
As you can see from the screenshot, their Web App includes instructions on how to install it on your smartphone and access it like a Native App.
Conclusion
By choosing to build with open technologies and Web Apps instead of the closed ecosystem of Native Apps, the SmartNFT Protocol provides brands and users with all the tools needed to create a dynamic and innovative ecosystem of SmartNFTs. No middleman taking 30% from everyone.
Thank you for reading this article,
Cheers,
Kumaly.
Really well explained. Thank you!