# Best Practices for user interface **URL:** \ **Category:** Classic Servoy\ **Created:** [September 7, 2011, 1:11pm UTC](https://forum.servoy.com/t/best-practices-for-user-interface/14600 "2011-09-07T13:11:18Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![kschuster](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kschuster](https://forum.servoy.com/u/kschuster)\ **Post date:** [September 7, 2011, 1:11pm UTC](https://forum.servoy.com/t/best-practices-for-user-interface/14600/1 "2011-09-07T13:11:18Z")
Newbie here. I’m wondering what the best practices are for setting up a user interface. I’m remembering back to my filemaker days of copying navigation and other application wide elements from form to form… don’t want to do that. Then later doing web development with lasso and using fusebox. this made the most sense to me separating design/navigation from the meat of the app How do you guys setup your apps? ---
**Author:** ![kschuster](https://avatars.discourse-cdn.com/v4/letter/k/9d8465/32.png) [@kschuster](https://forum.servoy.com/u/kschuster)\ **Post date:** [September 11, 2011, 8:46pm UTC](https://forum.servoy.com/t/best-practices-for-user-interface/14600/2 "2011-09-11T20:46:28Z")
In thinking more about this I seems to be perhaps the best method for setting up a “framework” for UI would be to create one “base” form which would contain the main navigational elements. Maybe nav across the top and down the left side. The insert a tabless panel in the main section of the base form. Then dynamically set the content of the tabless panel based on nav selections… Does this make sense? anyone? ---
**Author:** ![ROCLASI](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.servoy.com/roclasi/32/4371_2.png) [@ROCLASI](https://forum.servoy.com/u/ROCLASI)\ **Post date:** [September 11, 2011, 9:16pm UTC](https://forum.servoy.com/t/best-practices-for-user-interface/14600/3 "2011-09-11T21:16:26Z")
Hi kschuster, Using a form with a tabless tabpanel to navigate through forms is indeed a common way to setup your navigation. And with form inheritance you can setup a base form with your standard controls (new/edit/delete/etc) for your forms that you might want to load in that navigation tabpanel. So yes, this makes sense ![:)]( "Smile")