Starter Ionic Application Template w/Parse Integration
Updated: Dec 14, 2018
This sample application is provided as a starter to get your Ionic Framework andParse Application up and running easily. Most of the fuss in these applications is figuring out login and account creation… This template solves that for you with a pattern that then can be utilized for a full-blown application; this is not a throw-aways tutorial.
We have seperated out the templates, controllers, and services into a format that will be sustainable for your final solution.
Setting Up Parse Configuration in the Starter App
Parse Configuration Screen for Application
Using the values from the Parse Console, set the properties in the app.js file section shown below
Starter App Project Structure
The starter app is a Two-Tab based app with a Login Screen and an Account Creation Screen. The application will create Parse Users for you after it is configured properly.
The first Tab is setup as a list view that when a used clicks on an item in the list a detail screen is rendered. The ui-router routes are already configured for this application behavior.
The second Tab in this setup as a “Settings Screen” that will pass in the User Object from Parse when the user selects the Tab.
Application Settings View
The file structure is such that all of the user specific functionality is www/js/user/controllers.js for controllers andwww/js/user/services.jsfor services & factories. The associated views are in www/templates/user/login.html andwww/templates/user/signup.html .
UI-Router and Resolve
The simple way that we ensure the user is logged into the application is by using the abstract state tab , this state uses resolve functionality from ui-router to determine if the Parse User Object is available by callingUserService.init() . If the promise is resolved successfully, then we have a User object and the application can move forward.
If the UserService.init() function cannot resolve successfully, it returns the error noUser . Whenever the ui-router fails to route properly, an error is generated noUser.
We listen for the $stateChangeError and if it is in fact the noUser error then we route to the Login Screen using theapp-login state of the ui-router .
Since the tab state is abstract all child states of must also have successfully resolved the parent state, this ensures the user in logged in before executing any state of the application
Parse Service in Ionic Framework
Logging in a user is even more straight forward