Telerik Platform 2.0 comes with a new concept for app. While the Telerik Platform 1.0 app could contain multiple projects of the same type—three AppBuilder or Backend Services projects for example—the new app can only contain one of each project type.
As a consequence, the entire concept of projects has been retired. In a new app, you don't need to create a project to start writing code or analyze your app usage. Existing app projects, however, need to be migrated to the new Telerik Platform 2.0 app format.
- Frequently Asked Questions
- What Does Migration Do
- Migrating a Single App
- Migrating All Apps
- Automatically Migrating Apps
- Manually Migrating Apps
- How to Access Projects After Migration
Before you start migrating your apps you may want to read these question and answer pairs to learn more about how migration changes the way you use Telerik Platform.
- Q. What is "unified app development experience"?
- Q. Are there any new features or features that will be retired after the migration?
- Q. Which apps need to be migrated?
- Q. Can I skip or avoid the migration?
- Q. Do I have to migrate right away?
- Q. Will I lose code or data during the migration?
- Q. Will my app experience downtime during migration?
- Q. Will I need to issue an app update to my users after migration?
- Q. Can I revert a migrated app to its previous state?
- Q. How do I access my projects after migration?
- Q. I only use Analytics. Do I have to migrate my apps?
- Q. How does migration affect my subscription?
A. You can find an overview of the unified app development experience in Telerik Blogs: Telerik Platform 2.0 is Coming in December with Big Changes. This blog article also contains a link to an HTML prototype which will help you experience first-hand the new user interface (UI).
A. For an overview of the changes in Telerik Platform 2.0 see Telerik Blogs: What’s Next for Telerik Platform and Mobile Website Projects and Telerik Blogs: Telerik Platform 2.0 is Coming in December with Big Changes.
A. All apps created prior to the launch of Telerik Platform 2.0 must be migrated.
A. You can delay migration until a certain stage but you will have to migrate all your apps eventually. See Q. Do I have to migrate right away? for details.
A. No. You are provided with a grace period during which you can choose the most convenient moment to migrate an app. Until then you can continue working with it inside the familiar Telerik Platform 1.0 app concept.
At the end of the grace period you will be forced to migrate any non-migrated apps.
A. No. The migration only unlinks your existing projects from their current container app and links them to new apps.
A. Downtime is not expected. Your app can continue working with your Telerik Platform backend during migration.
A. No. The migration keeps full backward compatibility. You app will continue to operate as before.
A. No. To avoid inconveniences, plan carefully when to migrate your apps and how to distribute your existing projects to Telerik Platform apps.
A. You will still be able to access all the features of your projects arranged in a neat and logical way in the new portal. See How to Access Projects After Migration for details.
A. If you have purchased Analytics as a standalone product, your apps will be automatically migrated at the launch of Telerik Platform 2.0.
A. The migration to the unified app development experience has the following consequences on your Telerik Platform 2.0 subscription:
- Some features and subscription plans are being discontinued. See Q. Are there any new features or features that will be retired after the migration?
- Telerik Platform 2.0 imposes the same limit on apps as version 1.0 used to impose on projects. This means that if you were allowed to create up to five projects per type in version 1.0, you would be limited to creating up to five apps in version 2.0. Note that migrated apps can exceed your app number limit, allowing you to migrate all your projects the way you want to. Also see Planning.
Migration is a non-destructive process that combines projects from existing Telerik Platform 1.0 apps into a new Telerik Platform 2.0 app.
Each new app can combine up to four projects, one each of the following types:
- Backend Services
Telerik Platform 1.0 apps are suggested for automatic migration if they contain any combination of the following:
- zero or one AppBuilder project
- zero or one Backend Services project
- zero or one Analytics project
- zero or one AppFeedback project
Also, the AppBuilder and Analytics projects must be of the same type to qualify for automatic migration: AppBuilder Hybrid with Analytics AppBuilder and AppBuilder Native with Analytics NativeScript.
Telerik Platform 1.0 apps that contain multiple projects of at least one of the above types need to be migrated manually.
In both cases the Migration Wizard guides you through the process.
Before you start migrating your apps, take your time to plan for it.
- Ensure that all developers who have access to the app have closed all browser windows/tabs that are running Telerik Platform as well as all AppBuilder clients. If another developer is making changes to a non-migrated app while you migrate it, the changes may be lost.
- Identify which projects belong together and plan to migrate them to a single Telerik Platform 2.0 app. For example, if an AppBuilder project connects to a Backend Services project you may want to keep them in a single app. Once you migrate a project, only the Telerik team can move it between apps. If you need help, submit a Telerik Support ticket.
- When migrating only non-code projects (Backend Services or AppFeedback) to a new app, carefully consider what type of app you want to use them in: Hybrid or NativeScript. Once you create the app, you cannot change its type.
- Based on your subscription plan, Telerik Platform 2.0 may impose a limit on the number of apps that you can have. Plan as many target apps as you can afford to spend from your quota. If needed, delete projects that you don't use. Note that despite you being able to exceed your app number limit during migration, you will not be allowed to create new apps after that.
- Start with non-production/non-live projects. This will allow you to get used to the new app development experience before you migrate your production projects.
- Even though downtime is not expected, you may want to schedule production projects migration for less busy time periods.
- Migrate your production apps one at a time. After each, ensure that everything is operating as expected.
You can easily identify non-migrated apps by the red NOT MIGRATED label on the app tile.
To start migrating an app, hover the mouse pointer over the app tile and click Migrate. The Migration Wizard starts and guides you through the process. See Automatically Migrating Apps and Manually Migrating Apps to learn more about the process.
To start migrating all non-migrated apps, find the blue ribbon at the top that reads "Take a look at the new Unified App experience. Migrate to the new UI that helps you build apps faster." and click the Start button on the far right.
Automatic migration is the easiest way to quickly move your apps to the Telerik Platform 2.0 format. You can only use it for apps that comply with the requirements laid out in What Does Migration Do.
After starting, the Migration Wizard presents you with a list of Telerik Platform 1.0 apps that have been approved for automatic migration. If you have chosen to migrate a single app, it will be the only one in the list.
Take these steps to migrate your apps:
- Examine the list to ensure that you are OK with migrating all the suggested apps. Use the X button at the top-right corner of an app to exclude it from the list.
- Click the Auto migrate button to start the migration.
- After the migration completes, examine which apps have been migrated and which apps remain to be migrated.
- Close the Migration Wizard using the X button in the top-right corner or click Continue with manual migration to manually migrate the remaining apps, if any.
Refer to Manually Migrating Apps to learn more about manual migration.
You can rename the apps after they are created if you do not like the autoselected names.
Apps that do not comply with the requirements laid out in What Does Migration Do need to be manually migrated by you.
Take these steps to manually migrate your apps:
- After the Migration Wizard starts, click the Manual migration button. Note that manual migration will process all apps, regardless of what apps have been suggested for automatic migration.
- On the next screen, examine the projects contained in the first app selected for migration.
- Choose how to migrate the app:
- Click Create new app from each project if your projects are not logically interconnected and you want to use each of them to build a separate Telerik Platform 2.0 app. Each new app is named after the Telerik Platform 1.0 project.
- Click Map projects to new app when you want to create one or more apps from the set of projects that you have in the Telerik Platform 1.0 app. In this case you can select which project goes to what app as well as name the new apps.
- If you selected the Map projects to new app option, take these steps to map the app projects:
- In New app name, enter a name for the app that will be created or use the auto-suggested name based on the original app name.
- Select Telerik Platform 1.0 projects to map to Telerik Platform 2.0 features. Only projects from the app that you are currently migrating are displayed. You don't need to map a project to each feature.
- Click Next and repeat all substeps in this step until you map all the app's projects.
- Repeat the above steps until you map all apps' projects. You can cancel the wizard at any time.
- Click Finish mapping.
- Click Migrate apps to migrate all mapped projects at once.
- Click Done.
You can rename the new apps after they are created if you don't like the autoselected names.
Although your projects cease to exist in their initial form after migration, you can still find their functionality in Telerik Platform 2.0.
The following table shows where in Telerik Platform 2.0 to look for the Telerik Platform 1.0 project features that you are familiar with.
|Telerik Platform 1.0 Project Type||Telerik Platform 2.0 Feature|
|* If the AppBuilder project was started from Screen Builder|
The following paragraphs try to provide knowledge or solutions for situations that you may land in during or after migration.
- Symptom: After migration, when I click to open an app I am redirected back to the portal home.
- Symptom: My native Analytics projects are not available for migration.
- Symptom: After migration a green bar appears on top of the screen reading: “Apps limit reached - 5 used of 2 available. Upgrade your account subscription to continue.” What does it mean and why should I upgrade?
- Symptom: I cannot access Views in a migrated app. This message appears: “Views is not available for project name”.
Possible Cause: This issue is typically related to browser cache.
Recommended Solution: Log out of Telerik Platform, close all browser windows/tabs that are running it, and then clear the browser cache. After logging back in, you should be able to open your apps.
Possible Cause: Only Hybrid and NativeScript Analytics projects will be included in the Migration Wizard. Native Analytics projects for Android, iOS, Windows Phone, etc. platforms will be automatically migrated immediately after the Telerik Platform 2.0 release. You will not be provided with a grace period for them.
Recommended Solution: Not available.
Symptom: After migration a green bar appears on top of the screen reading: “Apps limit reached - 5 used of 2 available. Upgrade your account subscription to continue.” What does it mean and why should I upgrade?
Possible Cause: Your projects were migrated to a large number of apps that exceeds your subscription limit. See Q. How does migration affect my subscription? for more information.
Recommended Solution: You have the following options:
- Delete one or more apps to get under your account limit and then try to create a new app.
- Upgrade to a subscription plan that allows more apps.
Symptom: I cannot access Views in a migrated app. This message appears: “Views is not available for project name”.
Possible Cause: You have migrated an AppBuilder project that was not based on Screen Builder or you have modified the Screen Builder-generated code outside of the permitted boundaries.
Recommended Solution: Not available.
- Telerik Blogs: Telerik Platform 2.0 is Coming in December with Big Changes
- Telerik Blogs: What’s Next for Telerik Platform and Mobile Website Projects
- Telerik Platform 2.0 GUI Preview