The VERY first thing I'd ask is : "What is your killer feature?" What is it that the Motorhomer app will do that dozens of other camper apps currently available don't do? You don't need to answer here btw - but I think it's something that you need to know, for sure, before you commit yourself to hours and hours of work and investment. If you have that killer feature then GREAT! I can't wait to see it.
If the main feature is tying in with the Motorhomer forum, then I'd ask : "What will the app do that we can't do via a browser?" (and if so - why not just do it all in the website, that way we can do all the new funky stuff on our laptops as well).
Coming from a years worth of experience with various camper/motorhomer apps (and being a developer myself), I'd like to see any app have the following 'features':
- Full compliance with standard OS based interaction styles and systems (eg, don't use the OS back button to close the app, use the OS back button to go back to the previous 'view' the app just used)
- Keep iconography within an icon sub-file within the app's payload: don't litter the user's download folder with individual icon files.
- things like this may not seem important, or may be troublesome to code, but they go a long way to not upsetting the user. User's don't want, care, or need to know how anything works - they just want it to work seamlessly and seemingly magically (NEVER show them the trick!)
- Ensure the app is aware of on/offline status, and so (even if it's not got data), its works fine with what it does have when offline: eg, it doesn't try to work with online data and just sit there spinning and doing nothing.
- Ensure that any information useful to the usability of the app, eg what map icons stand for, is included within FAQ or Help information included within the app's payload. If we haven't used the app for a bit, so forgot what a map icon means, it's not good to have to go looking around the internet for it.
- Ensure that if your map interface includes custom interaction buttons, especially if some are only visible at certain times (such as when a POI is selected), that newly-showing buttons are not occluded by pre-existing buttons, or shown over the top of pre-existing buttons.
I desperately hope that I don't come across wrong here, I'm not trying to nit-pick, I'm trying to point out things that will make vast improvements to the user-experience. Part of my job for 10 years was QA-ing the work that went out of my department, so I think I'm very aware of what can kill the user-experience of an app or web-app.
Personally, I think it would be lovely to have map-pois for things like LPG stations, Water sources, Laundromats, Aires, WildCamp spots, etc, etc - but all of that data is HIGHLY dependant on the users filling in the data, as well as sourcing licensing deals from existing data-holders. One way around this will be to ensure that day-to-day users can upload 'reviews' (comments/feedback/whatever) for each and every POI, wherever it came from. It may be possible that the existing data holders will allow for their data to be updated by the MHApp users - There's every possibility of that I would think. It would be great to have all this data available within 1 killer app, providing that the app integrates seamlessly with the data-feeds and provides a user-experience that is superior to the existing sources of all that data.