How to migrate your application to HTML5
HTML5 has established itself as the technology of the future, even in industrial use. What can you do if you are using .NET, Qt or some other technology and want to make use of the advantages of the web world? Our whitepaper shows you how to quickly and efficiently migrate an established application to HTML5. To this end, we provide you with four building blocks, which you can use to work out a strategy for re-using as many components as possible.
In mechanical and plant engineering, there is one clear trend: away from individual machines towards comprehensive ecosystems across machines and devices. Accordingly, customers expect an optimal user experience on all platforms and devices – from Android smartphones to Linux-based control centers. These challenges cannot be readily mastered by just any technology. With web technologies, however, the situation is different: They allow for platform independence and responsiveness – benefits that you can take advantage of by migrating to HTML5.
This allows you to address new target groups without excluding your existing users. Migrating also provides you with the possibility to tackle long-planned changes, implement new features and improve user experience, giving your customers the opportunity for more satisfaction, efficiency and ease at work.
Determining the scope
To plan the migration and define the scope, you will have to analyze the requirements. What elements can you re-use from the existing application? What needs to be adapted or changed, e.g. to improve UX or accommodate for the new technology? What elements need to be added to allow for the integration of new functionality? From the design to UI controls and layouts, all the way to interfaces and the application code – our whitepaper provides you with a check list of topics and questions that you should bear in mind.
Using best practices
When it comes to migrating software from one technology to another, there is a wealth of general experience you can draw from. We would like to introduce you to well-established practices for successfully migrating design, layout and application codes. What is the best place and method to start? How should you plan the release? How can the design be transferred quickly and smoothly? We attach particular importance to porting the application logic: Our whitepaper shows you which components are best to remain on the client-side and which components should be implemented on the server, detailing how you can re-use as much of the original code as possible.