Free
$0/ month
Build your app and run it on a free krva.cc address. 5 build credits a month, no card.
Guide
How to build an app for your business without coding
You do not need to know how software is built to get an app that runs part of your business. You need to know how your business works. This guide turns that into a working app with Kreova, step by step, using a real app as the example.
The example in this guide is IronPeak Check-In, a front desk app for a 24-hour gym with two locations. It was built on Kreova on October 19, 2026 from the prompt in step 3. The members and visits in the pictures are sample data the app made for itself.
1
Pick one problem and the first version
Most business apps go wrong in the same way: they try to do everything at once. Start with the one job that costs you the most time or money today, and describe the smallest version that would already help.
Good first jobs for an app:
- Taking quote or booking requests and following them up
- Tracking jobs, who is doing them and when they are done
- Checking people in, out or off a list
- Sending invoices and seeing who still owes you
- Giving customers a place to see their own bookings or orders
Then write down what the first version must do, in one or two sentences. For IronPeak it was: the front desk scans a member's phone and sees at once whether they may come in, and the manager sees who comes in and when.
Leave the rest for later. Every change after the first build is a request in plain words, so a smaller first version costs less and is easier to check.
2
Map the people, records and actions
Before you write anything for Kreova, answer three questions on paper.
Who uses it?
Everyone who signs in: you, your staff, your customers. Give each group a name, such as manager, front desk and member.
What do you keep track of?
The things your business keeps a list of: customers, jobs, bookings, invoices, products. For each one, note the details you need. An IronPeak member has a name, phone, plan, expiry date and status.
What can each person do?
Who may see, add, change or delete each thing. This is where most of the value is: a front desk worker who can check people in but cannot change prices.
Here is IronPeak's map:
| Role | Sees | Can do |
|---|---|---|
| Manager | Everything: the dashboard, every member, every visit | Add, edit, freeze and renew members, and export the visits |
| Front desk | The check-in page and the member search | Check members in and out, but not change plans or prices |
| Member | Their own card and their own visits | Show their QR code at the front desk |
And the records: members, plans (Monthly $49, Annual $499, Student $35 a month, Day Pass $15), staff and visits.
3
Write the starter prompt
Put steps 1 and 2 into one message, in plain words. A good starter prompt says what the business is, who uses the app, what it keeps track of, what each person can do, what should happen on its own, the sample data you want to see, and the look you like.
This is the prompt IronPeak was built from, lightly shortened:
The IronPeak prompt
Build a gym check-in app for "IronPeak Fitness", a 24-hour gym with 2 locations (Downtown and Westside).
Members
- Each member has a name, email, phone, membership plan, home location, start date, expiry date, status (active, expired, frozen) and a unique member code.
- Plans: Monthly ($49), Annual ($499), Student ($35/month), Day Pass ($15).
- When a member signs in they see their membership card: their name, plan, expiry date, status and a big QR code of their member code, so they can show it at the front desk from their phone.
Front desk check-in
- A front desk page with a "Start scanning" button that keeps the camera scanning QR codes until they press Done.
- Each scan checks that the member exists, is active, isn't past their expiry date and isn't frozen, then saves a visit with the time and location. It refuses a second check-in for the same member within 60 minutes.
- After each scan, show a big green "Welcome, [first name]" with their plan and days left, or a big red message saying why: expired on [date], membership frozen, already checked in, or code not found.
- A search box for members who forgot their phone, to check them in with one tap.
- A list of the last 20 check-ins today that updates as people come in.
Manager dashboard
- Today's check-ins per location, check-ins by hour for the last 7 days, the busiest hours, active members per plan, and members whose membership expires in the next 14 days.
- A members table to add, edit, freeze or renew a member, with search and filters by plan, status and location.
- Export the visits to Excel.
Roles
- Manager: everything.
- Front desk: the check-in page and member search. Can't edit plans or prices.
- Member: only their own card and their own visit history.
Sample data
- 3 staff accounts, 40 members across both locations and all 4 plans, and 3 weeks of visit history, busiest from 5 to 8 AM and 5 to 8 PM.
Look
Clean and modern with a bold athletic look, a dark background with an electric green accent, and fast on phones.
Notice what it does not mention: databases, servers or code. It describes the gym. Kreova decides how to build it, and asks when something important is missing.
What makes a prompt work
- Write rules as rules. "Refuse a second check-in within 60 minutes" is something an app can enforce. "Make check-in smart" is not.
- Say what people should see when something goes wrong, not only when it goes right.
- Ask for sample data, so the app looks real the first time you open it and you can test it without typing.
- Describe the look in a few words. You can change it later.
4
Let Kreova build it, then refine it
Paste the prompt into Kreova and send it. Kreova plans the app, creates its database with the access rules for each role, writes the pages, adds the sample data and checks the pages it wrote. You watch it happen in the builder, with a live preview beside the chat.
IronPeak's first version took about 11 minutes of building, in four rounds. This is what it built:
Then the owner used it and asked for changes in plain words, the way you would ask a person. These are the real requests, as they were typed:
When I sign in as this one I see: No membership linked
A question, not a change: Kreova explained that a member's login is linked through an invite from the front desk. Questions cost no build credit.Can you make a rescan check out
Scanning a member who is already in the gym now checks them out. Done in about a minute and a half.When I try to scan again it says already checked in
The 60-minute rule still blocked members who had checked out. Fixed in 29 seconds.Make IronPeak installable on phones so staff can add it to the home screen and open the front desk scanner from the app icon.
Done in 35 seconds.
Each change is saved as a new version, so one you do not like can be undone. When Kreova needs a decision from you, it asks before it builds.
5
Test it the way your team will use it
An app that looks right is not finished until you have used it the way your staff and customers will. Before you share the link, check these yourself:
- Saved data: add a record, reload the page and check it is still there. Then change it and delete it.
- Roles: make a test account for each role and sign in as each one. Each person should see only what they are allowed to. In IronPeak, a member must not be able to open the members table.
- Forms: try an empty field, a wrong email and a date in the past. The app should say what is wrong, in words.
- When things go wrong: try the cases you described in the prompt. Scan an expired member and you should see the red message with the date.
- Phone and computer: open the app on both and press every button your staff will press.
When something is wrong, say what you saw, on which page, and what you expected. "When I try to scan again it says already checked in" was enough for Kreova to find the cause and fix it.
Kreova sets who may read and change each table on the server, not only in the page, so hiding a button is never the only protection. It still pays to sign in as each role and look for yourself.
6
Publish it and keep it running
Your app is live from the first build, at its own web address. IronPeak's is ironpeak-check-in.krva.cc. Share the link with your team. On Pro you can use your own domain instead.
What kind of app it is
Kreova builds web apps. They open in any browser on a phone, tablet or computer, and they can be installed to a phone's home screen with their own icon, as IronPeak was. They are not App Store or Google Play apps.
Keep improving it
Running an app is mostly small changes: a new field, a report, a different message. Ask for each one in plain words. Every version is saved, and the code is yours.
What needs your own accounts
- Taking payments in your app needs your own Stripe account. The money goes to you.
- Phone calls and text messages need your own Telnyx account, on Pro or Power.
- Emails go out from your own email account once you connect it, or from Kreova's mail service under your app's name until you do.
What it costs
Kreova charges for building, not for using the app. Each build uses a build credit, and questions that change nothing are free. IronPeak's first version and its changes used about 8 credits.
Pro
$29.99/ month
Your own domain, phone and texts with your own Telnyx account, and 20 build credits a month.
Power
$79.99/ month
Everything in Pro with 60 build credits a month, for owners who keep improving the app.
Extra credits come in packs when you need more in a month. Your own Stripe, Telnyx and domain costs are separate and paid to them directly.
What you still decide
Kreova builds what you describe. Some things only you can decide:
- Your rules: prices, opening hours, what counts as late, who gets a refund.
- Who gets access, and what each person may see.
- Your real data: when to replace the sample data with your own customers, and what you bring in.
- Your words: the messages, the emails and the name your customers see.
- Your policies: privacy, terms and anything your industry requires.
No. You describe how your business works in plain words, and you ask for changes the same way. The code is yours if you ever want it, but you never have to read it.
Not today. Kreova builds web apps that work on any phone, tablet or computer and can be installed to a phone's home screen with their own icon.
IronPeak's first version took about 11 minutes of building. A simpler app takes less. A bigger one is best built in parts: the core first, then one addition at a time.
Tell it what you saw and what you expected, in plain words. It fixes it as a new version, and the earlier versions are kept.
Yes. Each person signs in with their own account and sees only what their role allows.
Yes. Each app has its own database. You can see and edit the records in the builder's Data tab, and ask for an export, like IronPeak's Excel button.
Your business app
Describe your business. Kreova builds the app.
Fill in the brackets, or write it your own way.
✓ No credit card✓ Live on its own address✓ Change anything by asking