https://youtu.be/knH6Jms4vSY

I am currently building a CRM and normal day to day workflow app for the mechanic shop I currently work for. Do I need a landing page for this? If so, would it be simply just a login page? If it is just a login page I need, should I build it with the front end, or get that done in cursor? With GitHub not working with the project saves, I don’t want to mess up the finished UI I currently have. Thank you.

I need to know how you set up the ability to screenshot a part of the screen in cursor to give to the AI. Can someone tell me how please? Thanks!

I am currently using google AI studio to build an app that I want to put onto the App Store and google play store. Will I be able to put it out as an app as long as I hookup my back end and do everything else. Or is it just a website? Anyone with any info would be appreciated. Thank you!

Yesterday I met with my junior dev to review some new features we’re adding to a new module in our ERP migration app. As we went through the requirements, he kept asking: “What if… we’re not covering all the possible cases?” I told him: “Let’s look at this SQL result. How many rows do you see that are actually ‘what-if’ scenarios? Roughly 10%, right?” That doesn’t mean edge cases don’t matter — it means you shouldn’t START by trying to solve them all at once. Here’s the approach I recommended: 1. Build the general case first 2. Test the heck out of it 3. Identify edge cases (make an explicit list) 4. Implement edge cases one by one Why this works: If you implement everything at once and something breaks, you don’t know where the logic went wrong. And the worst bugs aren’t syntax errors — they’re incorrect logic. AI is great at fixing broken code. But if you inserted bad logic, that one is on you. For simple features, this might feel like overkill. But for complex systems (ERP, migrations, multi-role apps, etc.), this incremental approach is how you stay sane and ship reliably. Hope it helps as you keep growing as a dev.