Best Practices - KendoUI Mobile views

2 posts, 1 answers
  1. Peter
    Peter avatar
    2 posts
    Member since:
    Oct 2014

    Posted 11 Oct 2014 Link to this post

    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!
  2. Answer
    Martin Yankov
    Martin Yankov avatar
    177 posts

    Posted 15 Oct 2014 Link to this post

    Hello Peter,

    Your approach and app architecture greatly depends on the app you want to build. Since you are new to Kendo UI, I suggest you take a look at the Friends sample app that comes with the Telerik Platform. When you open the Telerik Platform you should have a workspace named Friends App. Enter it and click on AppBuilder. The Friends App needs a bit of configuring before it can start normally. Read more about it here - Sample Friends App Hybrid.

    You can review this app to get a hold on how you can declare your models, views and view models. This sample app showcases how you should organize your files when you build a real app. Once you start the app you might need to scroll down to "Don't have an account?" and click it to register.

    I just want to clarify some things that you might not understand correctly. When you build mobile hybrid apps, you always build a single page application or SPA that will be run in a mobile web view, not in the browser. A single page application does not mean you have all your code in a single file. It means that all your code (HTML, JS and CSS) will be loaded at the start of the app and navigation actually occurs when one view is hidden and another is shown. So whether you have all your HTML in a single file or in multiple files across folders only results in a better code and an easier maintainability. The Friends App is a beautiful example of that.

    Keep in mind that the app you want to build is not simple and the Friends App is just a sample app. You will need to take a look at multiple sample apps to understand what exactly you need to do. For example, you need to use a TabStrip layout and you can see a sample of it in the CoffeeHouse app. You can also take a look at the Telerik Verified SQLite Plugin and its sample app.

    I hope this information was useful. Let me know if you have any further questions or have any problems implementing the app you want to build.

    Martin Yankov

    Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.

Back to Top