The app we are considering developing will connect with a user populated DB that functions similar to a facebook app photo page that you can scroll and zoom in on. Where should this type of information be stored and how is it accessed by the app? (Looking for Best Practice?)

Hi @kleej, If you are looking to make the storage on the device itself, that's rather difficult, and to the best of my knowledge, nobody on the BT forums has figured out a hack to get that working with Buzztouch. Otherwise, it sounds like a standard mySQL database running on a server somewhere is the way to go. Every screen in Buzztouch is created using a JSON structure, so you can extract data from your database, send it to the app in JSON format, and build the screens you need. All the documentation for each screen is in the left-side menu for any app you create. If you give us some more info on what you are trying to do, we can probably provide you with some ready made scripts to help you out! Mark

Like @GoNorthWest suggests, it's usually MUCH EASIER to use a backend database and not a client-side (on the phone) database. There are lots of reasons for this. Adding a SQL Lite database to the project is not too difficult. However, writing thousands of lines of code to integrate / sync / marry your backend data with your client side data is very tough. Plus, consider this, a client side database on a phone can get large and over time the app begins to consume lots and lots of content. The key is the design of your app and how it interacts with your data. Think about it this way. Some of the largest, most successful apps in the world use a tremendous amount of data. Think Facebook for social, Angry Birds of games, Dictionary for utility. These apps store a VERY SMALL amount of data on the actual device and a VERY LARGE amount of data in the cloud, on their backends. This is for obvious reasons (no way to store your 10,000 FB friends on my phone). Plan, plan, plan. What are the data interactions, hows your backend setup, how will different devices used by different people interact with, change, remove the SAME DATA? Once you have that figured out, it's a matter of getting each screen to work with the backend accordingly.