1. If you need to do anything native, like use the camera or GPS for something, then I recommend you trigger navigating to those screens by either using Stacker's javascript bridge or by writing a custom URL action (http://www.lokimeyburg.com/Stacker/docs/custom-actions/).
You're still going to be responsible for doing the native screens. This is by design and kind of nice because my experience with apps are that most of the screens could just be done in HTML/CSS and there's usually only one or two screens that need to be implemented natively.
2. Check out my example to see how I'm doing using a regular UITabBarController. That might give you an idea of where to start.
You're still going to be responsible for doing the native screens. This is by design and kind of nice because my experience with apps are that most of the screens could just be done in HTML/CSS and there's usually only one or two screens that need to be implemented natively.
2. Check out my example to see how I'm doing using a regular UITabBarController. That might give you an idea of where to start.