Building the app

now you are ready to start using your well designed plan to build the app in {{jigxbuilder}} steps start with the data if you have a pre existing datasource, create the functions, and stored procedures if your data source is from scratch, start building the tables using creating tables docid\ jgu8dildvcvzabi6682xk or in microsoft azure sql docid\ bvwt1abmsq6sulitxvbk refer to your data plan for details next, build out the skeleton app based on must have functionality, follow your solution design for each screen, and create the corresponding {{jig}} file choose components and ui elements that meet the requirements see examples overview docid u2qde390fglp6uhkvbdf for a list of components, actions, widgets and jigs that can be used now add visual improvements and nice to haves e g , on an email field, add the email icon to interact with sending an email publish your app to the {{jigx}} cloud open the app on the mobile device and test each screen, data, and usability use debugging docid\ psqdlve46kfecb4fzb6tb to debug the app, make changes and test again when the building of the app is complete, move on to the test plan app skeleton considerations if you not sure what component, action or widget to use in your app build get inspired by using jig templates docid\ bfrn33frlt lba9i9u2uv , the jigx sample, and the jigx widget projects in github when selecting the elements to add to the yaml, consider the usability, and shortest steps possible to get to where you want in the app minimize navigation, aim for smart navigation, 30 40 second engagement on screens, especially forms have the required input fields on the form with optional fields in another section {{jigx}} design methodology encourages 30 second success this is important as mobile development is different from web, and space is limited tips create a prototype using jig templates docid\ bfrn33frlt lba9i9u2uv to see if a component or jig will work in your build, from there, you can customize the template yaml snippet practice continous testing by testing after building each screen