It’s simple with Ivanti Velocity, powered by Wavelink
Don’t get caught in the End of Support spiral with your legacy mobile computers. As Microsoft ends support for Windows Mobile and Windows CE over the next few years, you need a migration plan.
With Velocity, you can bring your existing telnet and web applications to a new generation of Android mobile computers, increasing productivity in four easy steps. Better still, you set the pace for each step in the progression, ensuring a successful deployment.
Step 1: Migration
Your workers will be expected to adapt to a new mobile device. Since change can cause confusion, minimise it by preserving your existing telnet client interface on a new device screen. Let your workers adjust to the new hardware. They’ll get comfortable with new devices faster if the software experience remains familiar.
For example, your existing telnet or browser-based apps still present in their existing format after they migrate over into Velocity. “Green screen” telnet apps are presented in the same textual interface as they did on previous generation devices. And web apps render in the same style as before, including our Industrial Browser, VelocityCE, Studio, and Naurtech CETerm. In all cases, your existing host application is preserved, and communication continues to be handled using industry-standard protocols.
Step 2: Optimisation
As your workers start getting familiar with their new Android mobile computers, you can begin building in enhancements to speed up your applications. Here’s where you examine steps in your workflows that can be automated (such as calculations), eliminate redundant tasks/steps, and so on with powerful scripting in the Velocity console.
With a focus on how workers interact with the app, you can make enhancements that speed their navigation and reduce training times. For example, create custom keyboards so that when workers reach a particular step in the workflow, only keys that are relevant to that step are presented. Numeric-only keys, or even simple “Yes” and “No” buttons may make sense at certain steps. The goal of optimisation is to help workers execute tasks faster, and train workers in less time.
Step 3: Modernisation
Once your workers have mastered their new devices and your workflow optimisations are deployed, you’re ready to modernise the user interface. In this step, you transform your existing telnet or browser app into a touch enabled app that looks and feels like it was made for Android. This modern, HTML user interface will feel like the apps your workers interact with on their personal smartphones—raising task speed and accuracy with familiar tap-and-swipe navigation.
Leveraging the power of the Velocity platform, your modernised application lets you highlight important onscreen data or add other visual cues, so workers can see what matters most—at a glance. Customisation, such as branding your apps with your company logo and colour schemes, happen here. And you can phase in modernised screens and tasks that fit your schedule—even run a mix of modernised and native screens within a task if necessary.
Step 4: Speech
Want an even greater productivity boost to your Android deployment? Empower your workers to do even more by voice-enabling your Velocity application with Speakeasy. Adding voice reduces the time workers spend reading and inputting data during a task. Speakeasy uses text-to-speech to read task instructions to your worker, and allows workers to speak commands and data back into your applications. Adding Speakeasy is … easy!
Using the Velocity framework, voice is simply another input for data capture. No need for additional servers or middleware, and no changes to your host applications. And because you don’t have to train Speakeasy to recognise each user’s language or accent, workers get up to speed fast.