Thanks @romanmg for yet again simplifying and explaining things. I wish I had access to this thread when I was first working out what and how to do SPA. I hate to think of how many hours I have spent reading threads with endless opinions and mixed replies that have left me more confused and wasting more time than necessary. I have two questions:
1. Screen size of mobile apps.
It is one thing starting wide (e.g. 1200px) and using responsiveness to scale down to mobile (easier) and another to start small (e.g. 320px) and use responsiveness to scale up (more demanding). What are the implications in terms of build time, Google SEO, etc. Is Google SEO impacted by whether you use a width of 320px (as I’ve seen you suggest) or 600px (as some on other threads suggest) or are both seen as mobile by the Google algorithm?
2. Popups in an SPA
I see a number of threads where people had difficulties making them responsive from small to large. I eventually discovered that I need to set the popup width to the widest size I want (e.g. 1200) and use ‘collapse margins’ to get my 320px content to stretch. But I’m wondering if using a 1200px popup in an otherwise 312px app negates all the hard work and potential Google gains made elsewhere. Is there any reason I ought to avoid popups, or any other element when aiming to produce a wrapped mobile app for the app stores? UPDATE - While I think of it, is there a way to stop all the scrolling on the page below a popup - can we somehow force the app to just scroll between top and bottom of the popup?
And for those reading this thread to learn how to approach SPAs, I recommend the following two threads from @petter (another expert bubbler).