Rails 4 For Startups Using Mobile And Single Page Applications: Complete guide to architecting and deploying a scalable mobile website with a single page application and Rails

This book aims to give a practical guide to developing and scaling a Ruby Rails application with a focus on mobile devices and the issues with using a Single Page Application (SPA). Websites are getting more and more traffic from mobiles devices that it has become important to prioritise development to mobilise your web page, even for sites which also have native apps. We will cover enough Ruby Rails to get started and some advanced topics to give you an overview of the language capabilities. It is a practical guide but some wider concepts will be discussed so you have a view of issues when deciding the best architecture to use and general programming tips. For a startup some tips such as focusing on the minimum viable product and suggestions for deciding your technology stack. As a full stack developer people need to be aware of the full product cycle including UX, development, deployment and even big data analysis. How do we prevent our app growing into one large monolithic mess of code, and how microservices can help decouple failure from other components. Here is a question when you start building the front end: “SPA or standard Rails?” some points to consider are: SEO considerations, Caching, logging, and debugging.

本書旨在提供一個實用指南，以開發和擴展一個針對移動設備的 Ruby Rails 應用程式，並著重於使用單頁應用程式（SPA）時的問題。網站越來越多的流量來自移動設備，因此將開發重點放在使您的網頁移動化變得重要，即使對於同時擁有原生應用程式的網站也是如此。我們將涵蓋足夠的 Ruby Rails 內容以供入門，並介紹一些高級主題，以便讓您瞭解語言的能力。這是一本實用指南，但也會討論一些更廣泛的概念，以便您在決定最佳架構和一般程式設計提示時能有全面的觀點。對於初創公司，我們提供了一些提示，例如專注於最小可行產品以及選擇技術堆疊的建議。作為一名全端開發人員，人們需要了解完整的產品週期，包括使用者體驗、開發、部署，甚至是大數據分析。我們如何防止我們的應用程式變成一個龐大的單體代碼混亂，以及微服務如何幫助將故障與其他組件解耦。在開始構建前端時，有一個問題需要考慮：“SPA 還是標準 Rails？”一些需要考慮的因素包括：SEO 考慮因素、緩存、日誌記錄和調試。