In this blog we will look at what an Application Blueprint mean in Progress Rollbase world and how it enables users to give a new and fresh look to your existing applications in Rollbase.
An important aspect of a RAD (Rapid Application Development) platform is to allow the application developers configure or customize their applications as much as possible. One such customization is to provide multiple templates for the navigation scheme inside the application. Such templates are termed as Application Blueprints in Rollbase. In short, to make an application more usable and modern as per the end-user’s requirements, application developer(s) can choose a specific Application Blueprint for his/her application.
Types of Application Blueprint in Rollbase (as of v4.3)
- Modern – Vertical Menus
The Traditional blueprint targets to provide an out-of-box Responsive UI navigation scheme to an application primarily target to desktop clients (browsers). In this blueprint the top-level navigable menus of the application are put in a hamburger sidebar menu. The sidebar menu renderes in a collapsed state which provides more space for the main application content. Following are the screenshots how the application looks on various screens/states
Modern – Vertical Menus
As the name suggests, the Modern – Vertical menus blueprint targets to provide more modern/trendy navigation scheme for the applications. This blueprint is mainly focused for applications which can be accessed in multiple client devices (browser/Tablet/Smart phone).
In this blueprint, the top-level navigable menus are put in advanced hamburger sidebar menu. The sidebar menu allows easy access of the menus even in collapsed state. Users can hover an item and can view/navigate to other parts of the application. The application switcher and footer links are rendered to top-right of the screen. One of most distinguishable advantage of this blueprint (over the Traditional blueprint) is that the application menus can have an icon attached
As mentioned above, the blueprint is targeted for applications which can be accessed from multiple client devices. See below how the application is rendered in a tablet/smartphone.
As a RAD platform, Rollbase allows its customers to try out the possible blueprints and lets the customers decide which is the best way for their applications to face to their end-users. Moreover, Rollbase does it in the simplest way. Changing the application blueprint is a single click configuration change. (Application Settings -> New UI Specific Settings -> UI Blueprint.)
It is designed such a way to let the users not to worry about the actual behavior change in the application business/UI logic. So, adopters need not worry much about the testing effort required for their application business logic.
Progress Rollbase envisions to add many such application blueprints so that they cater to customer needs out-of-the-box. As a powerful RAD platform Rollbase intends to allow its customers, who can have diversified use-cases, need not spend much time/money investment in building modern UI for their application front-ends.
Along the way of providing out-of-box blueprints to customer, Rollbase wants to retain its strength of allowing maximum customization to any of its feature. So, Rollbase will have a custom blueprint option by which users can design and implement their own application blueprint. This option lets the users build their own blueprint design with minimal coding.
To summarize the contents of this blog …
- We have seen what does an Application Blueprint mean in Progress Rollbase and why such a configuration is important for a Rapid Application Development platform.
- The blueprints available in Rollbase out-of-box.
- Various use-cases who the front-end differs in each blueprint.
- What is the vision of Progress Rollbase – Application Blueprints going forward.
Hope this blog has given enough insights about the topic. In case of any queries, please get back via comments or firstname.lastname@example.org