A farmers market app that people actually use has vendor profiles, what each stall has this week, a pre-order that reserves a box or a dozen eggs for pickup, and market-day notices, with no card payments in the app: customers pay at the stall, or a vendor adds a link to their own payment page. Describe that to App Builder Agent and the AI agent builds an Android app with a hosted backend where vendors update their own availability. A first version fits in the free plan; the Member plan is $1.49 per 30 days at the time of writing for unlimited builds.
Markets run on Saturday-morning uncertainty: will the tomatoes be there, did the bread stall sell out by nine, is the market on if it rains? Vendors answer the same questions on three social accounts and a chalkboard. A small app for one market, or for a group of farms with a shared pickup, replaces that with one list of stalls, one weekly availability update per vendor, and pre-orders that a vendor can pack the night before. It stays out of payments on purpose.
What the app needs
- Market info: dates, hours, location with a map link, a rain-day notice, parking and toilets. A pinned notice from the market manager.
- Vendor directory: name, photo, what they sell (produce, bakery, dairy, meat, flowers, prepared food), stall number or a map spot, payment methods accepted at the stall (cash, card, in the US also SNAP/EBT tokens from the info booth), and a link to their site or social page.
- This week's availability per vendor: a short list ("Heirloom tomatoes, first sweetcorn, no strawberries this week") with an updated-on date, and a Sold out toggle the vendor can flip from the stall on market day.
- Pre-orders for pickup: a customer picks items and quantities from a vendor's pre-order list, chooses a pickup window, and gets a confirmation; the vendor sees a packing list. Payment is at pickup, or the vendor sets an external link (their own payment page) for deposits. Nothing is charged in the app.
- Favourites and reminders: follow a vendor, get a notification when they post this week's list, and a Friday reminder that the market is on.
- Roles: market manager (edits market info, approves vendors, posts notices), vendor (edits their profile, availability and pre-order list, sees orders), customer (browse, follow, pre-order).
- Seasonal calendar (optional): what is usually in season each month in your region, as a browsing aid.
This is shared data across many vendors and customers, so the agent adds a hosted backend (database, auth, files) that runs on the platform's infrastructure. A map of stalls is a nice extra; the maps and location app guide shows what to ask for if the market is large.
The prompt to paste
Open App Builder Agent, sign in with Google, choose a mobile app and paste one message. Replace the market name, day, currency and categories.
For a UK market, use GBP, add "farm shop" wording and drop the SNAP/EBT line. For an EU market, use EUR and give the vendor page a "producer" label. For a single farm with a CSA or veg box scheme, replace the vendor list with one farm and add weekly box contents and a pickup-day selector.
What you get in the first minutes
The agent writes the screens, sets up the backend tables (vendors, products, weekly lists, orders, follows, notices) and shows the app in a phone preview in the browser. Approve a test vendor, post a weekly list as that vendor, place a pre-order as a customer and check it appears on the vendor's packing list. Then iterate:
Vendors will use the app standing at a stall with cold hands, so ask for big buttons and few taps on the vendor screens. The generated code is in the editor if anyone wants to inspect it.
Getting it onto phones
Click Download APK in the preview header for an installable Android build, and put the download link on the market's sign and social pages; Android asks once to allow installs from the browser. For a store listing, ask for a signed build (signed APK and AAB, package id like com.riversidemarket.app, keystore backed up) and follow the signed APK and AAB guide; the Google Play developer registration is a one-time $25 and new apps upload as an AAB. Builds are Android only. Since half your customers will have iPhones, also ask the agent to build the same project as a website published at a link on appbuilderagent.com; the browsing and pre-order screens work the same way there, and vendors can use whichever they have.
What it costs
At the time of writing the free plan includes 500K AI tokens a month with all features and no card; a free APK download is included. A market app with this many roles will use most of a month's free allowance to build and refine, so write the prompt carefully and batch changes. The Member plan is $1.49 per 30 days for 5M tokens, unlimited APK builds and source export; Pro ($5.72, 10M tokens), Business ($31.12) and Max ($11.01) suit a market association that keeps iterating or builds a second app. The hosted backend runs on the platform's servers; the market can export its data and delete the project. Prices can change; the AI app builder page lists current plans.
Notes for the US, UK and EU
Keeping payments at the stall is not only simpler, it matches how markets work. In the US, many markets accept SNAP/EBT through tokens or a card reader at the information booth, sometimes with matching programmes; the app should list which vendors take the tokens, not try to process them. In the UK and EU, contactless is the norm and a vendor's own card reader stays the payment method; where a vendor wants deposits for pre-orders, they paste a link to their own payment page and the app opens it. Pre-order data (names, orders, sometimes phone numbers) is personal data under GDPR and UK GDPR and subject to CCPA rights in California: keep a short privacy notice in the app, collect only what a vendor needs to hand over a bag, and let customers delete their account. This is general information, not legal advice. If a vendor sells prepared food, allergen information stays their responsibility; give them a free-text field for it.
If you outgrow pre-orders and want a proper catalogue with a cart, the online store app guide is the next step. Browse the shop and retail apps for list and product layouts, then paste the prompt with your market's name and day.
Frequently asked
Why keep payments out of the app?
Card processing inside an app means fees, a payout account per vendor and extra store rules, and markets already run on paying at the stall. Pre-orders are reservations; a vendor who wants deposits can add a link to their own payment page and the app opens it.
Can each vendor update their own availability?
Yes. Vendors get their own login, edit their profile and this week's list, mark items sold out on market day and see their pre-orders. The market manager approves vendors and posts market-wide notices.
Does it work for a single farm or a veg box scheme?
Yes. Replace the vendor list with one farm, add weekly box contents, pickup days and a farm stand schedule. The same prompt structure applies.
How do customers get the app?
Share the Android APK by link on the market's sign and social pages, or publish a signed build on Google Play. Because many customers have iPhones, also ask the agent to publish the same project as a website at a link.
What does it cost?
At the time of writing the free plan includes 500K AI tokens a month, which covers building a first version; a free APK download is included. The Member plan is $1.49 per 30 days for unlimited builds and source export. The hosted backend runs on the platform.
Build it now — free to start
Type the idea, sign in, and the agent builds it in your browser. Change anything by describing it.
Open the builder ›