The problem Framify: Get Shopify To Farcaster solves

The Problem:

Web3 presents additional complexity for web2 shop owners and the additional benefits of bringing their businesses onchain are usually offset by the risks and complexity of not knowing how to do basic web3 things like backup a seedphrase or organize private key managament, how to create farcaster frames etc.

The Solution:

An easy to use application that allows web2 users and owners of shopify stores to easily create product frames for farcaster that will enable them to accept onchain payments as well as easily create their first crypto wallet with coinbase Smart Wallet.

Enter our application Framify.

By leveraging coinbases Smart Wallet and with our easy no-code builder for Frames; web2 native Shopify store owners can bring their products onchain into Farcaster Frames and even sell their products right inside frames with transaction frames.

By not having to worry about seed phrases and generating our users wallets with passkeys we help simplify this entire process for web2 audiences and hide some of the initial complexity of moving onchain for shopify users.

Our dapp keeps track of frame analytics in a user dashboard so store owners can see how their product frames are doing.

We give the store owners the ability to attest onchain to the order details relevant to their frame transactions and provide onchain receipts powered by EAS.

Features:

• easy no-code Farcaster Frames builder
• support for multiple kinds of frames
• support for product frames with built-in support for transactions in USDC on BASE within frames
• shopify integration to facilitate GET-ing product information for frames via shopify ADMIN api (requires store url + API key)
• visual slideshow-like editor UI
• onchain attestations for receipt data for transactions using EAS

Challenges we ran into

We were unable to get the POST call to shopify with the order details working after completed farcaster frames transactions because the /create_orders endpoint in the shopify ADMIN api requires additional application permisions following a submission/approval process which we did not have time to complete.

We had issues using the latest version of onchainkit and the <Identity/> component.

We had issues using the eas.offchain() function with the EAS sdk for attesting to the receipt data using offchain attestations (onchain attestations were working).