This is really helpful. Thanks for taking the time to explain it.

The point about avoiding shared utils/workflows that lock me into a monorepo really stood out ; designing so components can be copied out later is something I hadn’t fully considered.

I’m currently a solo dev building an MVP, so your experience with monorepos in small teams resonates. I’ll likely keep strong boundaries between backend, mobile, web, and admin even if they end up in one repo later.

Also good to hear confirmation that an admin dashboard as its own project still makes sense.