A starting prompt
Paste this into the builder and change the names, rules and colours to yours. It produces a working first version; everything after is refinement.
Sell before you integrate
Every e-commerce integration — payments, stock, shipping rates, tax — costs time and monthly fees, and none of it is needed to make a first sale. A store app whose checkout sends a tidy order summary to your WhatsApp, with a payment link in your reply, is how thousands of small brands already sell on Instagram. This app just gives that flow a proper catalogue, a cart and an icon on the phone.
What gets generated
A Shop tab with categories and featured products, a listing with sort (price, newest) and filter (category), a product page with a swipeable gallery, options such as size or scent, quantity and Add to cart. A Cart tab with totals and a notes field. Checkout collects name, phone and address and sends the order as a formatted message. Wishlist is a heart on every product and a list under Account.
Products come from a Google Sheet: one row per product with name, price, category, description, image URLs and options. You edit the sheet; the app reloads. When you outgrow the sheet, the same loader can point at a Shopify, WooCommerce or custom API — the builder can make that change from a prompt.
Growing into payments
When message-checkout becomes a bottleneck, add a payment provider. Two routes: a payment link generated per order and opened from the checkout screen (no code beyond the link), or a native SDK added to the exported Android project by a developer. The screens do not change; only the last step does.
Play Store notes
A store app that links out for payment is fine on Play as long as you sell physical goods or services — Play's billing rules apply to digital content only. Your listing needs a privacy policy that covers the order details customers type in; the exported project's manifest lists only the permissions your features use, which keeps the data-safety form short.