# Laying out of busy interfaces (shipping app)

**URL:** <https://community.glideapps.com/t/laying-out-of-busy-interfaces-shipping-app/75818>\
**Category:** Ask for Help\
**Created:** [August 23, 2024, 3:59pm UTC](https://community.glideapps.com/t/laying-out-of-busy-interfaces-shipping-app/75818 "2024-08-23T15:59:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dan\_San](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/dan_san/32/24085_2.png) [@Dan\_San](https://community.glideapps.com/u/Dan_San)\
**Post date:** [August 23, 2024, 3:59pm UTC](https://community.glideapps.com/t/laying-out-of-busy-interfaces-shipping-app/75818/1 "2024-08-23T15:59:34Z")

</div>

Just looking for ideas and things to consider when designing an app for the shipping industry.

The app will need to collect a lot of data (fields) and then as the shipment (quotation, routing, vessels, booking, shipment, customs, billing) goes through various stages it will need to track and add on more fields/data

Looking for suggestions/ideas or feedback from others that may have done very busy apps/layouts.

Looking for an implementation that works like tabs, so when in a shipment, you can click on tabs/buttons to only display that collection of data/actions.  
I could get to about 300 - 500 columns, which will be larger then what I have done before, so any tips/guidance will be appreciated.

---

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [August 23, 2024, 6:52pm UTC](https://community.glideapps.com/t/laying-out-of-busy-interfaces-shipping-app/75818/2 "2024-08-23T18:52:25Z")

</div>

Hola!

If I were you, I’d sit down and on a table write the layout/schema of my tables (fields, relations, roles, security, layouts, naming convention, etc.) and screens.

You might start with this kind of tool at least: [https://drawsql.app/templates/wagtail](https://drawsql.app/templates/wagtail)

Saludos!

---

<div class="post-metadata">

**Author:** ![ThinhDinh](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/thinhdinh/32/49_2.png) [@ThinhDinh](https://community.glideapps.com/u/ThinhDinh)\
**Post date:** [August 23, 2024, 11:59pm UTC](https://community.glideapps.com/t/laying-out-of-busy-interfaces-shipping-app/75818/3 "2024-08-23T23:59:02Z")

</div>

I would segment those infos into their own “stages” with the column names so you can track them more easily. Let’s say Stage 1/Field name, Stage 2/Field name etc.

Then have a user-specific column for users to view info by stage, and drive the visibility conditions of containers/components using that USC value.