The problem inject web3 solves

Background

• Flow aims for mass adoption through walletless onboarding and HybridCustody mechanisms
• This is an effort to make it easier for ordinary people accustomed to web2 to enter the world of web3
• By making it easier for services that already have many users to introduce Web3 functions, it will be easier for them to participate in the world of Web3

Benefit

The following services can automatically generate Flow accounts for existing users and freely execute events such as NFT mint according to the actions of the service.

• EC sites like Amazon
• Free event like Kaggle
• Ticket sales web site for sports, live concerts, museums, etc.

For example, you can use it to mint an NFT according to the purchase of a product on an EC site, and use the NFT to participate in some event related the EC.

You can check the diffrence the EC app code before and after injecting web3: https://github.com/ShuntaroOkuma/inject-web3/pull/3/files

Challenges I ran into

• Enable web2 services to web3 with less code changes