flexClient is a mobile app that runs on your users' devices. It receives XML code from your enterprise systems, and interprets (adapts it's behaviour) based on what you've programmed in the XML. Your users will only need to install flexClient once, and we provide versions for whatever devices you need to support in your organization. Each flexClient app has its own data sandbox that keeps your data private for the individual, enterprise and specific application.
Unlike typical solutions, Velocity avoids requiring any middle-ware installations such as complicated frameworks, IDE's, or in some cases, additional servers and hardware. Developers can skip the approvals, installation, configuration and maintenance steps required with an un-necessary middle-man.
Native or cross-compiled mobile apps work great for consumers where you ship one app with infrequent updates. But, in the enterprise, the speed at which iterations are required and where ongoing and frequent response to users is essential, development teams need agile solutions that meet their agile needs. With Velocity, your users get your new code the instant you deploy, and are therefor always up-to-date. Invariably, native mobile app deployment in an enterprise is doomed to be downloaded at less than 100% compliance, so your development team is left to support multiple versions, and begging users to update to the latest build. Velocity's one-source automatic-deploy puts the developer back in the driver seat of agile development cycles.
The simplicity of the Velocity platform greatly reduces the chance for bugs, especially technically. However, as in all software, bugs are inevitable. Who knew Bob from accounting would enter a 4th decimal to his expense sheet? With compiled versions you can either fix the bug and distribute to everyone or sit on the bugs until enough pile up to warrant a new version. With Velocity you can make minor changes, test them in isolation, and deploy them without users even skipping a beat. A quick regex script will solve Bob’s 4th decimal without you having to expend IT resources on app distribution.
Many developers coming from the web world are used to agile development cycles. Get features out early and fix customer feedback in a 3 weekly iterative cycle; this means frequent releases. Thus, many find it hard to adapt to compiled mobile apps -- it's like old-school type software development where you need to finish a substantial version, test it thoroughly and release updates very infrequently because you really need to commit to the apps that are made public, as not all updates are distributed, nor are all updates installed by the users. Since developers can iterate quickly with Velocity, the platform's one-source automatic-deploy puts the developer back in the driver seat of agile development cycles.