Hi everyone and thanks in advance for any help and opinions you may have. I have been poking around for a few weeks, reading, researching, checking out your apps, etc. I plan on making an app from an existing website, it is basically a tourism destination app, so it is mainly content, but naturally would be enhanced with maps and perhaps a photo feature. What I don't want to do is start and have to redo the whole thing (although I am sure this is going to happen - so maybe I should say not have to redo the whole thing more than once). So to actually ask a question - what (if any) is the basic set up/work flow people are using for this kind of app? For example, the destination/home screen, and then a menu for dining, museums, points of interest, etc. - OR - a menu based on location/neighborhood - OR - just a map with icons that differentiate restaurants from museums, etc. And in any of these scenarios, would the pages themselves best be made as Custom HTML / Text or as HTML Docs? I am already thinking I am going to need to self host unless the RSS feed option is made available in the Plugins Market. And I also am thinking of trying to have a feature where people can add photos to galleries for specific places (as well as photo features of my own). Also - from what I have looked so far I would need help in some further customizing of the Location map plug in. I really want to have at the least customs pins, and at the most a numbered list alongside the map (or something similar). So that is basically it - your opinions on whether or not these things are doable or if I am off in the wrong direction, etc. are greatly appreciated. I know I will need to come back with more specifics as things progress. Thanks -

what (if any) is the basic set up/work flow people are using for this kind of app? For example, the destination/home screen, and then a menu for dining, museums, points of interest, etc. - OR - a menu based on location/neighborhood - OR - just a map with icons that differentiate restaurants from museums, etc. And in any of these scenarios, I think HTML gives the greatest flexibility given the plugins available. would the pages themselves best be made as Custom HTML / Text or as HTML Docs? Using your own editor and own online storage the HTML Doc plugin is as good or better than the Custom HTML Text plugin. Will you need offline capabilities? Fred

Hi @Afinta Welcome to be BT, well I see you have been poking around a bit so a belated welcome! A good few people have built similar apps, very recently in fact. You looking at iOS, Android, both?

Thanks Fred! Re: "Will you need offline capabilities?" - still not sure yet.

MacApple I guess it would be both ideally but I am a Mac head from way back and that is probably where I would start if I have to choose. I am an HTML person but not a "programmer" - I struggle once the Javascript starts... :)

Re: "Will you need offline capabilities?" - still not sure yet. By embedding the HTML Docs you have offline capabilities. Downside is that embedding Docs requires publishing a new binary to make modifications. Fred

Embedded HTML Docs that references online content (images, iframe ) can be modified with out a new binary. Fred

@afinta: Because you're a "Mac Head" and will begin with iOS, I would try to minimize the amount of HTML to the biggest extent possible. OR, if you're comfy with HTML, do the very best you can to make it compelling, beautiful, rich. @Fred is correct in that it's super flexible and easy to work with. BUT, Apple's been very very hard lately on approving heavily used HTML apps. Super bogus but it's not up to you to control what they "like." So, for sure you're app with utilize HTML for simple things (like messaging, text explanations, etc) but focus on thinking about how you can create something compelling, rich, fun, useful without relying on HTML too much if again, if you can). Think images, maps, quiz, fun stuff. You may end up needing a few custom plugins, you may not, it will mostly depend on your ability to make something NICE that Apple's impressed with. Remember, if they are impressed, so too will your end users be (in most cases). If they are not, you're not going to get very far beyond the submission process. OK, now that I've scared you...dont' be. LOL. Like @MacApple says, there is an endless amount of possibility in front of you and a huge / steep learning curve. Stick with it, it's worth the effort.

Thanks David - I will keep all of this advice in mind.