Without details of the application and complexity of workflows, this cannot be said.Some guideline:
- we generate screens for listing, adding, interacting with data automatic, adjusting them is work of days
- fully porting a complex existing application, taking the end users along and implementing advanced features fully customized keyboard navigation, wysiwig editing for form printing, insurance workflows across the complete Swiss legal framework still is a multi-year project
- What is the argument for moving my Progress application to the web instead of implementing SAP?
With Build.One you take a step to the web and retain full control and customizability, without running into another legacy trap as Build.One drives the backend technology stack, the customer defines the views and logic.While building complex business applications are time consuming to build, offering a migration path to the web while retaining the backend code and database, significantly reduces risk as it cuts scope of the project.