Showing results for 
Search instead for 
Did you mean: 

Be able to define a navigation structure on app level / divide screen (templates) into sections

Defining navigation is currently a bit of a hurdle to take. Ideally we should be able to:


1. Define an overall app navigation structure, combining multiple options such as:

* Bottom bar (horizontal) navigation icons

* Top bar navigation items

* Back/return items

* Hamburger menu

* ...


2. Apply the best option for the screen you are working on.


In a way this means that you are also able to divide a screen into multiple sections (header/footer/middle section/...), which is a great way to structure the work. Finally, this will drastically reduce the work to copy-paste-configure-position the navigation structure on each screen!

Status: New
Not applicable

Although it does not solve your particular problem, the common practice is to build a screen the way you need it and then copy that screen as many times you require, therefore keeping the layout and position of items.

Kudo Collector

True, that's what we have to do currently. And if the customer requests a modification in the navigation structure, after you have done the copy-paste, you have a big problem. 


In fact, the agility of building apps often requires changes due to the learning curve. In this context I've encountered it many times that we decided to change the core navigation as it would better serve the end user.


Not applicable

Actually, it makes perfect sense now that you've explained it, thank you. An option of moving/resizing/formatting controls/boxes on all screens at the same time would definitely help. You just got my vote.

Kudo Collector


Advocate I
Advocate I

a Hamburger Menu like the one offered in Mendix will be nice!


Please make this top pirority. We need a menu and not copy and paste the controls on each screen.

This is preventing us to build large and complex apps.

Resolver I

You can take the copy and paste work around a step further as well to make later changes easier and reflect in the whole app.


Just as mentioned before, create a screen with the navigation elements you want to see, let's call this BaseTemplate.


Then duplicate that base template to another screen, which we shall call ReferentialTemplate. In this template, for each control, set all properties you imagine you are going to be changing (size, location, colours, OnSelect etc.) to reference their counterparts in the BaseTemplate screen. So RT_Label1.Fill = BT_Label1.Fill


New instead of duplicating the BaseTemplate screen to new screens, duplicate the ReferentialTemplate screen.


Now if you need to make any changes after creating all your needed screens, you just change the BaseTemplate which will be referenced throughout your app without needing to rewrite everything.


This method can involve a bit more upfront work, but can save a great deal of time later on.