<p>If designing a web app with the view to launch mobile app later, assuming you're doing everything from scratch and have no legacy burden, how would you go about structuring everything?</p>
<p>For instance, suppose you're creating a Quora or yahoo answers clone, or a wiki, or blog engine. </p>
<hr/>**评论：**<br/><br/>AdamSmithLiberal: <pre><p>You could create a REST api in a Go web framework and then serve a Single Page Application (in Angular or react etc)</p></pre>shovelpost: <pre><p>Write a <a href="https://developers.google.com/web/fundamentals/codelabs/your-first-pwapp/" rel="nofollow">Progressive Web App</a> with a Go backend. It's much cheaper than developing a separate mobile app.</p></pre>Xerxero: <pre><p>Does it work on iOS yet ( service worker in the background) ? </p></pre>shovelpost: <pre><p>It works on Safari using polyfills.</p></pre>catkins88: <pre><p>Bit of a broad question.</p>
<p>If you wanted something batteries included you could try something like <a href="https://gobuffalo.io/" rel="nofollow">https://gobuffalo.io/</a></p>
<p>If you want something much less opinionated you could use <a href="http://www.gorillatoolkit.org/pkg/mux" rel="nofollow">http://www.gorillatoolkit.org/pkg/mux</a> and <a href="http://jmoiron.github.io/sqlx/" rel="nofollow">http://jmoiron.github.io/sqlx/</a> to get you going with an API, the build your front end using Vue or React or whatever, and reuse it when the mobile app comes up?</p></pre>deranjer: <pre><p>I started a project like that recently and decided on the gorilla websocket package and use websockets to communicate from frontend to backend using JSON (react for frontend). In retrospect gRPC might have been more useful.</p>
<p>REST also should work fine and frameworks like Goa help a lot with that.</p></pre>
