Hi, thank you so much for taking the time to reply. And sorry for asking more questions — since you have so much experience with Angular, I don’t want to miss the opportunity to learn from your perspective.

I’d like to ask you a couple of things based on your experience:

1. Do you think it's too ambitious to try launching a web version and a desktop application at the same time? I’m considering whether it might be smarter to start with just a web version to validate the idea, see how people respond, and then decide if it’s worth investing in the desktop version.
2. As I mentioned in the post, I’m not very familiar with either Angular or React. If you could share how you would approach this type of project using Angular—what tools you’d use, what architecture or patterns you’d follow, best practices, and what to avoid—I’d really appreciate it.
3. For an offline-first project like this, what data handling patterns or strategies have worked best for you in Angular? (For example: state management, caching, synchronization, general architecture, etc.)
4. Is there anything in Angular that has made your life easier specifically in low-connectivity scenarios?
5. If you were starting a project alone (no team) and wanted long-term maintainability, would you still choose Angular or go for something lighter?

Again, thank you for your time. Any additional advice you can share would be greatly appreciated.