I posted something similar before but wanted to reiterate. I don’t like the separation of Design and Build. In my opinion ALL apps should now use design mode in some format and worst case you could just skip it and go straight to app. However, by having them separate we lose the plan functionality and we also sort of lose the context of the app - Design shouldn’t just be about the visual aspect but the whole construct of the app ie. the UI/UX developer, the infra guy, the architect etc all talking with each other at the start of the project. I believe this should be built as a flow within Replit to encourage good practices from the outset.
5 Likes
I agree. The “design” mode needs to be the main and only entry point, and that is how I treat it:
…I drop my client’s PRD and my big system prompt (preferred architecture, etc) into design mode, and sure enough it focuses on the design first. But it does so with full knowledge of the product requirements and my preferred architecture. Once I like the design, maybe asking Agent to make a few tweaks along the way, I then tell it to proceed to building out the full app - which is where it switches into plan/build mode.
So yeah, it does seem weird having the different entry points. But I guess we have to remember that Replit is a work in progress that is moving at 100mph.
1 Like
Yeah of course - it’s all hopefully constructive criticism as you know we love Replit!
Further to my point above sometimes you want to plan when in Design mode and sometimes you want to design after you’ve built the initial mode - so I think the best option here would be to have Design as an option where you have plan and build currently when talking with agent rather than separated into plan or build at the start - then you could switch nicely at any point during the build.
1 Like