What Mikxx can do
Every feature and whether it's ready, partly there, or not yet.
What works today, checked against the code (2026-10-30). Ready means it works end to end and has tests. Partly says what's missing. Not yet is planned or open; see the roadmap. This page is also on the site at /docs.
Building
| Feature | Status | Notes |
|---|---|---|
| Describe it and the agent builds it | Ready | A form or a mini app from one message. It plans first, asks only what changes the result, and shows a preview before anything is saved. |
| Change it by asking | Ready | "Add a phone question", "make step 2 optional": only what you name changes, and past answers stay attached to their questions. |
| The agent remembers your decisions | Ready | Choices you settle ("prices in ₹") hold in every later chat. See and remove them in the form's Settings. |
| The agent looks at your data | Ready | It can read a summary of your responses or lists before answering. It never sees email addresses, phone numbers or files. |
| Visual builder | Ready | The live form is the editor: type on the page, settings beside the selected question, "+" between questions, keyboard moves, autosave, undo and redo, on desktop and phone. |
| Layout suggestion | Ready | The builder suggests single page, one question per screen or steps, with the reason, on desktop and phone. |
| Starters and templates | Ready | Start from a template or the café-order starter. |
Forms
| Feature | Status | Notes |
|---|---|---|
| Question types | Ready | Short and long text, email, phone (with a country code), number, address, signature, country, choices (list, pills, cards, plans, emoji, segmented, dropdown), checkboxes, choice grid, ranking, consent, date, time, rating, scale, NPS, yes/no, slider, hidden fields, plus headings, text and images. |
| Fill answers from the link | Ready | A question's link key fills it from ?key=value; hidden fields keep values like utm_source. |
| Save and finish later | Ready | Answers saved as people go, an emailed link to finish on any device, and unfinished responses for the owner (kept 30 days). |
| Display modes | Ready | Single page, one question per screen, steps, or a mini app. |
| Design | Ready | Presets, fonts, component libraries, backdrops, progress, layouts, welcome and thank-you screens. Colours are kept readable automatically. |
| Templates | Ready | 17 ready-made forms and mini apps to start from, on the Templates page: café, bakery and tiffin orders, class, salon, gym, clinic and photoshoot bookings, events and workshops, feedback, applications and leads. Each uses its own design (kit, font, backdrop, layout, pictures). |
| Uploads | Ready | Upload pictures for the panel, cover, welcome and image blocks (5 MB each, 200 MB per workspace), and respondents upload files to file questions (8 MB; pictures, PDF, office documents, text). Only your workspace can open respondents' files. |
| Split-screen and fullscreen | Ready | A side panel (picture or brand) beside the questions, shown in the builder too; a banner on phones. Works with one question at a time and multi-step. |
| Validation | Ready | Required, lengths, ranges and patterns, checked again on the server. |
| AI follow-up questions | Ready | One short follow-up when an answer is vague, on questions you choose. |
| Payments | Ready | Razorpay or straight to your UPI ID. The price is worked out on the server and kept with each order. |
| File questions | Ready | The file uploads as it's picked (up to 8 MB: pictures, PDF, office documents, text) and only your workspace can download it. |
| Conditional logic and branching | Ready | Show a question, block or step only when earlier answers call for it. The server drops hidden answers before storing, pricing and bookings. |
| Calculated fields and answer piping | Ready | A calculation question works out totals and quotes from answers and option prices (recomputed on the server); {answers} show in later questions and the thank-you screen. |
| Embedding on your site | Ready | In the page (sizes itself), as a pop-up button, or a plain iframe, from the Share tab. |
| Spam protection | Ready | A hidden trap field, a minimum time to fill in, rate limits, and an optional human check (Cloudflare Turnstile) per form. |
Mini apps
| Feature | Status | Notes |
|---|---|---|
| Lists you manage | Ready | Classes, menus, rooms: records with typed fields, edited in the Data tab. |
| List and detail screens | Ready | Rows, cards or a grid, each record with its own screen. |
| Search, filters and paging | Ready | A search box on longer lists, filter chips, "Show more". |
| Choices from a list, priced | Ready | A question takes its options and prices from a list. |
| Bookings that fill up | Ready | Each booking takes a spot; full ones drop out; cancelling gives the spot back. |
| Customer sign-in | Ready | Customers sign in with an emailed code and see their own orders. |
| Customers add their own entries | Ready | Reviews everyone sees, or records each customer keeps to themselves; they edit and delete only theirs. |
| Lists that link | Ready | A class links its teacher; a teacher's screen lists their classes. |
| Dashboard screens inside an app | Ready | Tabs with counts, totals and breakdowns from a list, worked out from what each viewer may see. |
| Screens that change with the data | Ready | Hide records, show badges and detail fields by a record's values, and show tabs only to signed-in (or signed-out) customers. |
Publishing and sharing
| Feature | Status | Notes |
|---|---|---|
| Publish and unpublish | Ready | A live form has a link and a QR code. |
| Close on a date or when full | Ready | A closing date and a response limit, with your own closed message; late responses are refused on the server. |
| Passwords and invite links | Ready | A password, or one-time invite links per person; the questions load only once unlocked, and each invite takes one response. |
| Versions | Ready | Customers see the published version while you edit. Publish changes when ready; bring back any earlier version. |
| Your own domain | Ready | Live forms at forms.yourshop.in (Pro 1, Business 5) from Settings → Domain: a CNAME, a certificate from Cloudflare, a form at the root and each form at /<link-name>. |
Results, payments and automations
| Feature | Status | Notes |
|---|---|---|
| Responses inbox | Ready | Statuses, paid and claimed payments, CSV export. Bookings can be edited, with spots moving with them. |
| Home and results summaries | Ready | What needs confirming, today's orders, trends. |
| Payment history and payouts | Ready | |
| Email the team | Ready | On each response, or when an order is paid. |
| Webhooks | Ready | Signed, retried for about 7 hours, with a history and a retry button. |
| Emails to respondents | Ready | Payment receipts, and confirmation emails (an automation): your message and their answers, at most 3 a day per address per form and 300 a day per workspace. |
| Public API | Ready | Developer keys (read, or read and write) from Settings → Developers for /api/v1: forms, responses and templates (start a form from a template filled with your own name, menu or classes), 120 calls a minute per key. |
| Drop-off and funnel analytics | Ready | Opened, started, each screen and sent, with the biggest drop called out; no personal data kept. |
Team and security
| Feature | Status | Notes |
|---|---|---|
| Workspaces and roles | Ready | Invite teammates by email as admin, editor or viewer; change roles, remove people, and switch between workspaces. |
| Sign-in | Ready | Email and password, Google, password reset. New accounts confirm their email with a code. |
| First-run questions | Ready | Business, first goal, payments today, team, where they heard of Mikxx, and a plan, beside a live preview; shown in the console. |
| Plans and billing | Ready | Free, Pro and Business by Razorpay Subscriptions (monthly or yearly, auto-renewing). The plan sets the fee kept on Razorpay payments and the agent messages a month (30, 300, 1,500). Public pricing page. |
| Isolation | Ready | Every request is checked against your workspace on the server; tested for each feature. |
| Activity history | Ready | Settings → Activity: who changed what, for owners and admins. |
| Help, bug reports and feedback | Ready | Help in the sidebar: report a bug (with the page and browser), send feedback with a rating, or ask a question; replies show there and by email. |
How it's built: architecture.md. Decisions: adr/.