Is there any maximum number of locations screens or individual locations that can entered on a BT App?

I haven't hit a max, but have found a reason to be frugal. At one point, before I reorganized, my app FISH FINDER hit nearly 800 pages. This made the config file HUGE, meaning it took a long time, and often failed to update the app (since it was capped at 25sec). The workaround is to increase the download time allowed (its in the forum somewhere.. can dig it up if you need it), or, as I plan on doing, disconnecting from the Buzztouch control panel and updating via Apple resubmission. Hope that helps!

Thats very helpful. So it might not be the location that hog space/time its the pages themselves. Interesting... Have you considered using a web page with your locations instead of having the locations within the app? I poked around a little on the forum and it seemed a little over my head. Entering hundreds of addresses lat/longs must have taken a while and the page alternative seems like an easier way. On the hand, once they are in they are there for good and easy to update from the control panel I suppose. Thanks you sharing, much appreciated.

See this post about how to use a remote data source for your locations: http://www.buzztouch.com/forum/thread.php?tid=65181E4ADF97874B08E6D2B There is not limit. However, you'll want to be mindful of how many location menu items you use...extreme amounts of items leads to confusion for most users. It's generally best to use the same map to show all the locations and not seperate maps.

Thanks Dave, great advice. I was thinking of a screen for each US State. Not sure yet, still developing the concept. Keeping the screen down to a minimum sound best.

The reason I have individual location screens is that I want to provide both info and directions. Users first find the main map, with all 200 locations on it, and each pin leads to its own individual map. I may get to the point where I include the map on the html info, but that seems to load slowly in places with low signal strength, whereas the native google map works pretty well even with little to no signal.

FAO: TheHoogler Hey just wanted to let you know I downloaded your app today - interested as my own upcoming app is likely to have numerous screens and locations. After download I could only access: - About this app - Options and Information All other screens showed 'Screen not found?' I refreshed several times and after about the 5th time it all loaded properly. Anyway - wanted to give you a heads up on this, all good now but thinking most people wouldn't know/want to refresh multiple times - also noticed there was a review saying it didn't work. Hopefully if you can get to the bottom of this it may help my multi-page app so please share. Hope you get it sorted. Cheers.

Yeah, that's part of the uploading prob. I'll be submitting an update today that should clear that. I'll have to check that review. I may have to switch entirely to html, just so we don't see those screens.

TheHoogler and few others are working through some troubles we didn't anticipate. The idea that a lightweight mobile app would have 800 pages isn't something we consider. I think ultimately the answer will be to host lots of smaller config files, one for each screen, on your website. Next, use the dataURL property of each screen to pull these files 'as needed' from the your backend. This approach would lighten up the configuration data considerably. In simple terms, the only data in the config would be the menu's, and each menu would pulls it's items from a config file (for that menu) from your site. Tapping an item would then pull the next file for the map, also on your site. This is called 'lazy loading' and is a great approach to dealing with lots and lots of data. We realize this is tough to do without any documentation but I figured I would throw the concept out while we tried to finish some detailed instruction on how to do it. It takes literally like 20 or 30 hours sometimes to document, explain, write, video all the varies ways to do these things and it's been really hard to keep up on the instructions. But...we've got some new help around here and do hope to get back to this important work.