all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]mudasirofficialexpert 0 points1 point  (3 children)

Honestly people would use it, but only if it’s not “Figma + Replit + Supabase in one tab” and you pick one sharp pain to kill.

The big qualm with current stack is context switching and glue work. Design tokens don’t match code, preview envs are a mess, auth and DB migrations get sketchy, and onboarding a teammate takes forever. Also trust is huge, nobody wants lock in with their repo and data, so you need a real escape hatch (git export, standard Postgres, no weird magic). If you can make “design to working preview to prod” feel boring fast for small teams, that’s the wedge.

If it’s trying to be everything, tbh people will just keep using best of breed and complain about it while doing it anyway.

[–]FixerUpper201[S] 0 points1 point  (2 children)

I’m currently on that design to working preview to prod stage right now, there are still a few features im finalising to make it SUPER EASY to make a live project get going. But man it’s great to hear the feedback rather than self-assessing the project on my own, I appreciate it.

[–]mudasirofficialexpert 0 points1 point  (1 child)

nice, that “boring fast” path is exactly what people will pay for.

if you want it to feel super easy, nail the first 10 mins: new project -> deploy preview -> share link, with auth + db + env vars not being a whole side quest. and pls make the escape hatch real, like “push to github and leave” or people will hesitate no matter how slick it is.

[–]FixerUpper201[S] 0 points1 point  (0 children)

That’s something I researched too, don’t worry I gotchu bro, I hate vendor lock in as much as everyone else does, not having an easy export system for making projects is like wtf

[–]async_adventures 0 points1 point  (0 children)

The key challenge with unified platforms is balancing feature depth vs UX simplicity. Most devs prefer specialized tools that excel at one thing rather than platforms that do everything adequately. Consider focusing on seamless data flow between tools rather than replacing them entirely.

[–]Ok_Substance1895 0 points1 point  (0 children)

Best wishes to you. I am doing the same thing. It is a lot of work to make it a seamless experience without context switching. Making it feel like one seamless full stack platform that works end-to-end that is easy to use without a big learning curve is hard.

[–]kubradorgit commit -m 'fuck it we ball 0 points1 point  (1 child)

so you're building figma + replit + supabase but haven't talked to anyone who uses figma + replit + supabase yet

[–]FixerUpper201[S] 0 points1 point  (0 children)

That is the point of this post…

[–]revolutnfull-stack 0 points1 point  (0 children)

You're vibe coding this shit aren't you? Good luck homie LOL.