Revision history [back]

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros - * User always knows where they are - * User immediately knows where they can navigate - * Possible to notify the user about new updates on each tab - * Complements the gesture based UI

Cons - * Takes some space on the page

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros * Pros

• User always knows where they are * are
• User immediately knows where they can navigate * navigate
• Possible to notify the user about new updates on each tab * tab
• Complements the gesture based UI

Cons

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Complements the gesture based UI

Cons

• Takes some space on the page

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Complements the gesture based UI

Cons

• Takes some space on the page

Tabs could use the same familiar little light ball as with the page navigation for showing the current tab.

Here's a quick mockup how it might look

And here's how transition between tabs would look like

And here's how transition would work when going out of the tabs view

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Complements the gesture based UI

Cons

• Takes some space on the page

Tabs could use the same familiar little light ball as with the page navigation for showing the current tab.

Here's a quick mockup how it might look

tab.

And here's how transition between The light ball would move over the next tab icon when changing tabs and give a hint for the user about the transition.

Opening a new page from any tab would look like

And here's how work just as usual. The transition would work when going out of give the user a cue that they're moving away from the tabs view

view.

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Complements the gesture based UI

Cons

• Takes some space on the page

Tabs could use the same familiar little light ball as with the page navigation for showing the current tab.

The light ball would move over the next tab icon when changing tabs and give a hint for the user about the transition.

Opening a new page from any tab would work just as usual. Tapping an item could navigate to a new page. You should not, however, add a page to the stack unless specifically activating some item as this would have two conflicting gestures. The transition would give the user a cue that they're moving away from the tabs view.

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Complements the gesture based UI
• Flattens the navigation hierarchy into a more accessible format

Cons

• Takes some space on the page

Tabs could use the same familiar little light ball as with the page navigation for showing the current tab.

The light ball would move over the next tab icon when changing tabs and give a hint for the user about the transition.

Opening a new page from any tab would work just as usual. Tapping an item could navigate to a new page. You should not, however, add a page to the stack unless specifically activating some item page as this would have two conflicting gestures. usual. The transition would give the user a cue that they're moving away from the tabs view.

Tabs should only be used on the first page with no other pages on the page stack. Tabs should not be used when swipe between tabs would conflict with other gestures such as navigate backwards/forwards.

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Complements the gesture based UI
• Flattens the navigation hierarchy into a more accessible format

Cons

• Takes some space on the page

Tabs could use the same familiar little light ball as with the page navigation for showing the current tab.

The light ball would move over the next tab icon when changing tabs and give a hint for the user about the transition.

Tapping an item could navigate to a new page as usual. The transition would give the user a cue that they're moving away from the tabs view.

Tabs should only be used on the first page with when there are no other pages on the page stack. Tabs should not be used when swipe between tabs would conflict with other gestures such as navigate backwards/forwards.

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Faster navigation between views (1 tap/swipe as opposed to 2)
• Complements the gesture based UI
• Flattens the navigation hierarchy into a more accessible format

Cons

• Takes some space on the page

When to use it?

• When you have 3-5 pages with a lot of information to display

Tabs could use the same familiar little light ball as with the page navigation for showing the current tab.

The light ball would move over the next tab icon when changing tabs and give a hint for the user about the transition.

Tapping an item could navigate to a new page as usual. The transition would give the user a cue that they're moving away from the tabs view.

Tabs should only be used when there are no other pages on the page stack. Tabs should not be used when swipe between tabs would conflict with other gestures such as navigate backwards/forwards.

The sailfish silica needs a tab component. Currently silica supports only list and menu based navigation but many apps require a flat navigation hierarchy. The lack of official silica tab component has caused many developers to resort on their own implementations of tab components, which often don't work well with other silica components.

Pros

• User always knows where they are
• User immediately knows where they can navigate
• Possible to notify the user about new updates on each tab
• Faster navigation between views (1 tap/swipe as opposed to 2)
• Complements the gesture based UI
• Flattens the navigation hierarchy into a more accessible format

Cons

• Takes some space on the page

When to use it?

• When you have 3-5 pages with a lot of information to display

Tabs could use the same familiar little light ball as with the page navigation for showing the current tab.

The light ball would move over the next tab icon when changing tabs and give a hint for the user about the transition.

Tapping an item could navigate to a new page as usual. The transition would give the user a cue that they're moving away from the tabs view.

Tabs should only be used when there are no other pages on the page stack. Tabs should not be used when swipe between tabs would conflict with other gestures such as navigate backwards/forwards.