What you can build with Onplana Maker
Onplana Maker builds and publishes front-end web
apps, the kind that run in a browser and live at a shareable onplana.app URL.
That covers a huge range: marketing pages, small tools, dashboards, forms,
prototypes, and more. This page gives you ideas, a copy-and-adapt example prompt
for each, and tips for getting a great result on the first try.
What people build
Section titled “What people build”| You want | Try describing it like this |
|---|---|
| A landing page | ”A landing page for my dog-walking service: a hero with a photo, three pricing tiers, a contact section. Warm and friendly, works on phones.” |
| A portfolio or personal site | ”A one-page portfolio for a photographer: a gallery grid, a short about section, and an email link. Minimal, black and white.” |
| An event page with RSVP | ”A page for a birthday party on June 12: the details, a map link, and an RSVP form. Playful, bright colors.” |
| A calculator or estimator | ”A tip calculator: enter the bill and party size, pick a tip percentage, show the per-person total. Big buttons, mobile first.” |
| A dashboard from your data | ”A dashboard that reads /assets/sales.csv and shows monthly revenue as a bar chart and the top products in a table.” |
| A quiz or survey | ”A five-question personality quiz that shows a result at the end. Fun and colorful.” |
| A searchable directory | ”A searchable directory of the coffee shops in /assets/shops.json, with a filter by neighborhood.” |
| A small utility | ”A Markdown-to-HTML converter with two panes and a live preview.” |
| A prototype to test an idea | ”A clickable habit tracker: add habits, check them off daily, see a streak. Keep the data in the browser.” |
Write a strong first description
Section titled “Write a strong first description”The agent does its best work when your description answers three things: what the app is for, its key parts, and the style you want.
-
Say what it is for and who it is for. “A booking page for a yoga studio” beats “a website”.
-
Name the key sections or screens. “A hero, a class schedule, and a sign-up form.” This gives the agent a structure to build.
-
Describe the style. Colors, tone, and whether it must work well on phones. “Calm, lots of white space, mobile first.”
-
Point at any data or assets. “Read the classes from
/assets/schedule.csv.”
A weak prompt like “make me a website” leaves every choice to the agent. A strong one like “A one-page site for a food truck: today’s menu, a location map, and hours. Bold and fun, mobile first.” gets you close on the first build.
Iterate in small steps
Section titled “Iterate in small steps”Building is a conversation. After the first build, refine it one change at a time so you can see each result in the live preview:
- Change one thing per message: “make the header dark”, then “add a contact form”.
- Refer to specific parts: “the pricing table”, “the hero image”, “the footer”.
- Use the Plan tab to line up what comes next and check work off as it lands.
Quick edit or “Make it better”?
Section titled “Quick edit or “Make it better”?”- Quick edits are small tweaks, colors, copy, spacing, a bit of layout. They are fast and cost little credit.
- Make it better is for bigger changes: a new feature, a restructure, a different approach. It runs a deeper build and costs more credit. Tick it when a change deserves real work, leave it off for a nudge.
What Maker is great at (and what it is not)
Section titled “What Maker is great at (and what it is not)”Maker builds front-end web apps and publishes them as static sites. That is perfect for pages, tools, dashboards, forms, and prototypes. A few things to know:
- Data lives in the browser or in your files. Apps can store data in the browser (so it persists on that device), read files you upload, or call public APIs. There is no private server or database behind a published app.
- It is one app per project. Each Maker project is a single app with its own plan, files, and issues.
- For team work, graduate. When an app becomes a team effort, open it in the full Onplana workspace for people, roles, and project management. Maker itself stays a focused, solo building surface.
Can Maker build something with user accounts and a database? Published apps are static front-end sites, so they do not run a private backend. Apps can persist data in the browser or call external APIs, which covers most tools and prototypes. For a full backend, use Maker to build and validate the front end, then take it further with your own stack.
How detailed should my first prompt be? Detailed enough to cover purpose, the main sections, and the style. You do not need to specify everything, you refine the rest by talking to the agent.
Can I start from an idea I am not sure about? Yes. Pick Start with a plan to have the AI draft the steps first, or just describe a rough version and iterate. Some projects stay plans and never get built, that is a fine outcome too.
Related
Section titled “Related”Was this helpful?
Thanks for your feedback!