Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tool bar(s) #217

Open
Tosin-Balogun opened this issue Dec 23, 2024 · 0 comments
Open

Tool bar(s) #217

Tosin-Balogun opened this issue Dec 23, 2024 · 0 comments
Labels
component Add or improve a design component documentation Improvements or additions to documentation native aka team beyond

Comments

@Tosin-Balogun
Copy link

Tosin-Balogun commented Dec 23, 2024

What

When it comes to native app layout and structure, the apps often comprise of system bars, tool bars and content views as a whole. The system bars includes the status bar (battery, signal etc) and drag handle or navigation bar controls (on android).

The system bar sits on top of the toolbars which exist within an apps structure.

Toolbars are a common term to describe the top and bottom controls for in app navigation and action would usually live.

Problem

We describe them as top and bottom navigation, but these do not match up with how they are described or work. Each bar control often host action elements that does not involve navigation.

App UI structure

For the top tool bar, we have navigation/action bar and the bottom tool bar, we have the tab bar or toolbar. These are called app bars on android documentation but still mean the same thing in common dev terminology.

Image

Detail

iOS describes tool bar as

A toolbar provides convenient access to frequently used commands and controls that perform actions relevant to the current view.
Image

A navigation bar appears at the top of a window or screen, helping people navigate through a hierarchy of content.
Image

A tab bar lets people navigate between top-level sections of your app.
Image

All 3 have direct relationship under the iOS app layout structure and code with the toolbar parameter deciding where each component sits within its view structure

Android describes tool bar as

A Toolbar is a generalisation of action bars for use within application layouts. While an action bar is traditionally part of an Activity's opaque window decor controlled by the framework, a Toolbar may be placed at any arbitrary level of nesting within a view hierarchy. An application may choose to designate a Toolbar as the action bar for an Activity using the setActionBar() method

Top app bars display navigation, actions, and text at the top of a screen
Image

Bottom app bars display navigation and key actions at the bottom of mobile and tablet screens
Image

Navigation bars let people switch between UI views on smaller devices
Image

All 3 have direct relationship under the Android layout structure (called scaffold) and code with the toolbar parameter deciding where each component sits within its view structure

References

Related to

#53 #17

@Tosin-Balogun Tosin-Balogun converted this from a draft issue Dec 23, 2024
@Tosin-Balogun Tosin-Balogun added documentation Improvements or additions to documentation component Add or improve a design component native aka team beyond labels Dec 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component Add or improve a design component documentation Improvements or additions to documentation native aka team beyond
Projects
Development

No branches or pull requests

1 participant