This question is locked. New answers and comments are not allowed.
Hello - I am new to KendoUI Mobile and I am using AppBuilder to build my first App. I started my workspace and used a couple of the samples and noticed that there are a few different approaches between Coffeehouse, Airlines, Sushi, ect. I believe I saw MVVC and multiple html pages, a single page app that uses jQuery as well, and some with just one big js file containing all the View Models.
My question is, what is the most up-to-date sample and what are the best practices for implementing MVVC? I am building a SQLite heave app that has many search and sort features, but also other areas of functionality not related to the DB like using the scanner to search Amazon API from a barcode and also sharing pictures. Bottom line is I think I need a nav bar to separate these areas of functionality, but most importantly on the DB functionality side I need to do lists that will be constantly refined and searches that will drill down from one list to a sub list to a sub list to ultimately a result (like Sushi App).
Would the CoffeeHouse app be the best approach here? I think I need to separate various backend data sources (the DB, the API calls, a share button maybe) and I also need to have a few separate pages (no single page app) because there are multiple key areas of functionality.
Any suggestions are greatly appreciated!
My question is, what is the most up-to-date sample and what are the best practices for implementing MVVC? I am building a SQLite heave app that has many search and sort features, but also other areas of functionality not related to the DB like using the scanner to search Amazon API from a barcode and also sharing pictures. Bottom line is I think I need a nav bar to separate these areas of functionality, but most importantly on the DB functionality side I need to do lists that will be constantly refined and searches that will drill down from one list to a sub list to a sub list to ultimately a result (like Sushi App).
Would the CoffeeHouse app be the best approach here? I think I need to separate various backend data sources (the DB, the API calls, a share button maybe) and I also need to have a few separate pages (no single page app) because there are multiple key areas of functionality.
Any suggestions are greatly appreciated!