Problem
We needed a better way to track engagement on our content across platforms—our old RPA workflow was limited, messy, and unscalable.
So we built our own internal dashboard by combining:
Lovable → For generating a clean UI from our product brief
Cursor → To help write custom React chart components (with AI)
Momen → A full-stack no-code platform where we stitched everything together
Why Momen?
Unlike Lovable or Cursor alone, Momen gave us structure, control, and flexibility:
Fully configurable backend (data modeling, workflows, automation)
Code components for embedding real React
Visual editor for app logic, roles, and data flows
🛠️ Key features:
Add a content link → auto-fetch and store details
Visualize engagement over time
Automated updates via Actionflow
Fully interactive UI built with real code components
⚙️ Built 90% visually. Coded only where it mattered.
📽️ Want to See It in Action?
- 🎥 Watch the 10-min video walkthrough:
- ✍️ Read the full blog post:
How We Used Lovable + Cursor + Momen to Build Our Social Metrics Tool
See how to build a content dashboard with Momen, Lovable and Cursor. Explore how to increase the dev efficiency while gaining flexibility and control.
momen.app
- 🌐 Explore the live project: https://editor.momen.app/tool/L6ARjmem6RK/WEB?code=sgllui0YcYinL
Top comments (2)
this is actually pretty sick, i’ve always liked mixing visual tools with a bit of code. you ever worry the stack pieces will get out of sync down the road or you just roll with it and tweak as you go?
Great question! One of the reasons we built this dashboard the way we did was to keep things flexible without creating too much fragmentation. We mix no-code structure (like schema, logic, and backend flows) with custom React components within a unified environment in Momen. So even when we bring in AI-generated code via Cursor, everything still connects back to one stack.
That said, things can still drift if you’re not careful. Our approach has been to keep core logic (data handling, automation) inside Momen’s native tools, and isolate custom code to purely presentational parts (like charts). That way, updates stay manageable — and if we ever need to tweak a component, it’s scoped and doesn't break the rest of the app.
When we do need to tweak a code component in Momen, we can debug it locally (just like any regular React project), then use Momen’s real-time preview to instantly see how those changes render inside the actual app. So even though we’re mixing in custom code, the feedback loop stays tight — no redeploys or messy rebuilds.
So yep, we tweak as we go — but with guardrails in place.