They do have think about some of those issues more, especially security if the client contains all the of application logic, hence the row level access control. And when you charge per API call CPU usage matters, a database update is significantly more expensive than a cached get.<p>It&#x27;s genius to get started quickly, but quickly becomes an architectural nightmare. If you need to change a query and the logic is in the mobile app then its going to be days before Apple approves a new build, and even longer before the user updates to the latest version. If your logic is on the server side then you roll out the new code and you&#x27;re done.