This is exactly the kind of use case I had in mind when I wrote this, so I’m really glad it helped. Your plan to combine Cursor + Copilot is honestly what I’d recommend too, especially for a solo build of that size. Cursor will give you speed and UI momentum early on, and Copilot will help you tighten things up when the codebase starts getting complex. One thing I’d suggest (based on what I saw during testing): be intentional about when you switch between them. Cursor is great for generating features quickly, but before things pile up, running a “Copilot pass” on critical parts (auth, API routes, data layer) can save you from subtle bugs later. Also not surprised at all about your Replit experience. It’s powerful, but those “interesting decisions” can become expensive to fix once the app grows.
If you don’t mind sharing, what kind of project are you building? I’m curious how you’re planning to structure it solo.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This is exactly the kind of use case I had in mind when I wrote this, so I’m really glad it helped. Your plan to combine Cursor + Copilot is honestly what I’d recommend too, especially for a solo build of that size. Cursor will give you speed and UI momentum early on, and Copilot will help you tighten things up when the codebase starts getting complex. One thing I’d suggest (based on what I saw during testing): be intentional about when you switch between them. Cursor is great for generating features quickly, but before things pile up, running a “Copilot pass” on critical parts (auth, API routes, data layer) can save you from subtle bugs later. Also not surprised at all about your Replit experience. It’s powerful, but those “interesting decisions” can become expensive to fix once the app grows.
If you don’t mind sharing, what kind of project are you building? I’m curious how you’re planning to structure it solo.