If AI chat has become this natural, shouldn't the dashboard disappear?
That is a fair question. I asked it myself while building FORMLOVA.
I seriously considered whether the product should live entirely inside chat. In many ways, it could have. But I decided to keep the dashboard. Not because I wanted to preserve an old interface. Not because I was hesitant to commit to chat-first. I kept it because the product works better with a clear division of roles.
Chat is where work moves forward. The dashboard is where state is checked at a glance.
That distinction matters more than people think. And I believe it is one of the reasons FORMLOVA can feel fast without feeling careless.
Removing the Dashboard Was Technically Possible
I want to start with the honest version.
Yes, I could have removed the dashboard.
FORMLOVA is built around a chat-first workflow. You can create a form, revise fields, move through the pre-publish review, ask for response counts, send follow-ups to a filtered group, and connect downstream actions without opening a traditional admin screen. During development, I spent a lot of time thinking about how far that model could go.
It could go quite far.
But "possible" is not the same thing as "good."
Once I tried to push status checking fully into chat, the experience started to degrade. What is the sender name right now? Is auto-reply enabled? What are the current publish settings? Did I already set the privacy policy URL? Any one of these questions is easy enough to ask in conversation. The problem begins when there are two, three, or five things you want to confirm in a row.
At that point, the interaction stops feeling elegant. It starts to feel fussy.
That was the turning point for me. Chat-only was feasible. It just was not pleasant enough.
Status Is Faster to Confirm Visually
This comes directly from my own background in digital marketing.
When I think about day-to-day operational work, I see two very different kinds of actions. One is doing. Creating something. Editing something. Asking for one answer. Triggering a follow-up. The other is checking. Looking across the current situation. Comparing settings. Scanning a wider pattern before deciding what to do next.
The first category fits chat beautifully. The second often does not.
Take settings, for example. If I want to know the current auto-reply status, the sender name, and whether certain publish-related settings are already in place, I do not want to ask those one by one in a conversational thread. I want to see them together. I want to recognize the state quickly and move on.
Analytics works the same way. For a single question, chat is excellent. "How many responses came in today?" is a perfect chat interaction. But if I want to step back, scan the full picture, notice a pattern, and decide on the next action, a visual surface helps. It is easier to think when the state is laid out in front of you.
This is not a story about chat being weak. It is a story about roles.
Chat is strong when you want to retrieve something immediately or push the work forward. A dashboard is strong when you want to look across the current state and judge it quickly.
So in FORMLOVA, I did not keep the dashboard as a second primary interface. I kept it as the place where state can be seen clearly.
Chat Is Best for Moving Work Forward
The main interface is still chat. That part is deliberate, and I do not want to soften it.
Form creation is the clearest example. You can start with something vague. "Create a contact form." "Make a registration form for next week's workshop." "I need a simple inquiry form." From there, FORMLOVA can ask clarifying questions, make a draft, suggest the completion screen, prompt for duplicate-prevention decisions, and guide the review flow naturally.
That back-and-forth is much more comfortable in conversation than in a rigid screen.
The same is true for quick checks. "How many responses do I have?" "Show me unanswered inquiries." "Find people who rated us below 3." Those are the kinds of tasks that should not require opening a dashboard, navigating a menu, and orienting yourself again.
There is another advantage that matters even more to me: chat can connect multiple actions in natural language.
"I want to host an event." "Create the signup form." "Set the confirmation email." "Send reminders only to registered attendees."
That sequence is natural in conversation. It maps to the way people think. And now that voice input is practical, the experience can become even lighter. In many cases, you do not even need to type. You can simply say what you want.
That is why I think of chat as the place where work gets done.
That Is Why Form Creation Is Chat-Only
In FORMLOVA, you cannot create a form from the dashboard.
That was not a limitation caused by time. It was a product choice.
Technically, I could have added a dashboard-based creation flow. But I believed that doing so would blur the product's center of gravity. I do not think the most important problem is how to spend more time on the creation screen. I think the more important problem is how to reduce the friction between creation and everything that comes next.
What I learned from real operational work is simple: the truly important part starts after the form exists.
Traffic. Response handling. Analysis. Follow-up emails. Improvement cycles. Internal coordination. External handoffs.
The form is the entry point. The longer work begins after that.
So I wanted the entry point to be light. Fast to start. Easy to shape through vague language. Easy to continue from. If someone wants to perfect a highly crafted creation flow as the center of their tool choice, there are already strong products in that direction. FORMLOVA is not trying to win by becoming more creation-heavy. It is trying to make the rest of the operation flow better.
That is also where the MCP-native structure matters. Because FORMLOVA lives in the same AI environment as other MCP-enabled tools, the product does not need to become an everything-suite by force. It can stay focused on its core role while still connecting outward.
That is a better use of the medium.
I Kept the Dashboard to Reduce Friction, Not to Preserve Habits
One misunderstanding I especially want to avoid is this: "If chat-first is real, the dashboard should be unnecessary."
I do not agree.
My goal was never to make every action happen through chat just to prove that it could. The goal was to reduce wasted effort and let people move faster. If pushing everything into chat increases the number of confirmation exchanges, creates more small interruptions, and makes users ask for state repeatedly, then the product becomes more ideological and less useful.
That is not what I wanted.
So I separated the jobs.
Use chat for doing. Use the dashboard for checking.
That split makes the product easier to understand. It also makes it less stressful. The dashboard is not required to get started. Many people may never open it during their first meaningful use. That is completely fine. But when someone wants reassurance, or wants to verify a cluster of settings visually, or wants a broader analytical view, the dashboard is there.
"Optional but reassuring" is a better role for it than "mandatory control center."
In practice, I think there are only a few moments when opening the dashboard really makes sense:
- when you want to confirm the current settings in one place
- when you want to look across analytics as a whole
- when you want to check personal account items such as plan details or receipts
That is enough. The dashboard does not need to be the center to be valuable.
FORMLOVA Is Closer to a Web Concierge Than a Workflow Builder
I do not think of FORMLOVA as a workflow builder.
Workflow builders often encourage a plumbing mindset. Which condition branches where. Which trigger connects to which action. Which path sends which notification. That can be powerful. But it is not the feeling I want at the front of the experience.
What I care about more is this: someone has an intention, and they want to reach a goal.
"I want to run an event." "I want to handle inquiries faster." "I want to collect responses and follow up properly."
FORMLOVA starts at that point. The form becomes the entry point. Then the next steps can unfold from the same conversation, including handoffs to other MCP-enabled services when needed.
That is why the product image in my head is not a builder. It is a web concierge.
Not a system that asks you to wire every pipe by hand, but a system that helps connect intention to outcome in the right order.
The form matters. But the form is not the final destination. It is the front door.
Try It First
The main point of this article is not that FORMLOVA has a dashboard.
The point is that chat should lead, and the dashboard should support. Chat is where work moves. The dashboard is where state can be seen clearly. That separation exists not to make a philosophical statement about interfaces, but to help people move faster with less friction.
If that idea resonates, the best next step is simple.
Try it.
You do not need to study the dashboard first. You do not need to memorize a setup screen before you understand the product. Start with one sentence:
"Create an inquiry form."
From there, FORMLOVA can draft the form, preview the completion screen, ask about privacy and duplicate-prevention decisions, and help shape the design from screenshots or URLs if you want. If you later want to confirm the settings visually, the dashboard is there. If not, keep going in chat.
That is the experience I wanted to build.
