Can the app use my existing WooCommerce store?

Yes. Connect the store's REST API under Server, as your own API. The credential stays on the server, and the app reads products and places orders through it.

Do I have to use Apple or Google payments for products?

No. Physical goods are paid through a payment provider or your store's checkout. The stores' purchase systems are required for digital goods and subscriptions.

Is there a template for shops?

Not yet in the public catalog. Describe your store in chat and attach screenshots of shops you like, or of your own design.

Use case

Build an e-commerce app with AI

A product catalog, product pages, a cart, checkout and order history, connected to the store you already run. Describe your shop and the assistant builds a native iOS and Android app around your products.

Start building

Screens an e-commerce app needs

Home with featured collections and promotions
Category browsing, search and filters
Product page with photos, variants and reviews
Cart and checkout
Order history and order details
Wishlist
Account, addresses and settings

How to build it with FluxNative

Start from a description. Describe your own app in chat and attach screenshots of apps you like or of your own design. You get real native source code you own, in TypeScript. Start a project
Refine it in chat. Ask for one change at a time and watch the live preview update. Every turn lands as a revision you can undo, and the Design tab changes colors, type and spacing without a prompt. Work with the assistant
Connect the backend. Save your Supabase, Firebase or Appwrite credentials under Server once. The assistant then creates the tables, security rules and functions the app needs; it never sees the secret values. Server
Build it and install it. Build a signed APK and install it by scanning a QR code, or build an IPA without a Mac and send it to TestFlight. A build that fails costs nothing. Native builds overview
Publish. FluxNative uploads to TestFlight and Google Play, tracks every store step, and submits for review only after you confirm; the app record is created once in each store console, and Apple and Google decide. Publishing overview

Data and backend

If your shop already runs on a platform with an API, such as WooCommerce's REST API, connect it under Server as your own HTTP or GraphQL API. The credential stays on the server and the app reads products and writes orders through it.

Starting fresh? Supabase, Firebase or Appwrite can hold the catalog and orders, and the assistant creates the schema and the rules that keep each customer's orders private.

Payments and store rules

Physical products are paid through a payment provider such as Stripe or your store platform's own checkout, not through the App Store or Google Play purchase systems, which are for digital goods and subscriptions.

A first prompt to send

Send it as it is, or change the details to match your idea.

Build a shopping app for my clothing store: a home screen with new arrivals, categories with filters, product pages with sizes and colors, a cart, checkout, order history and a wishlist. Products come from my WooCommerce store's REST API.

Frequently asked questions

Can the app use my existing WooCommerce store?: Yes. Connect the store's REST API under Server, as your own API. The credential stays on the server, and the app reads products and places orders through it.
Do I have to use Apple or Google payments for products?: No. Physical goods are paid through a payment provider or your store's checkout. The stores' purchase systems are required for digital goods and subscriptions.
Is there a template for shops?: Not yet in the public catalog. Describe your store in chat and attach screenshots of shops you like, or of your own design.

What will you build next?

Start with a prompt or images. No credit card required.

Start building Explore plans