Use of cards (opinions needed)

[richervin]

I want to create an app which has a number of tabs - let's say 4 tabs, each with independent functionality and each with multiple screens and several possible screen flows.

For example, I have 4 tabs with an average of 6 screens each for a total of about 24 screens. This is on an ANDROID or IOS device.

I want each of the tabs to operate independently. For example, if the user is partially finished with something on Tab "A", they can switch over to Tab "C", do some work there, then come back and finish what they were doing on Tab "A". They operate independently of each other (though they might share information with each other, potentially).

Here is the question:

Would you create 4 cards for this app, each with the entire collection of widgets for it's related functions, and use hide/visible functionality to control the user flow through the application?

Or would you create 24 cards for this app, one for each screen, and control the screen flow through the cards? Keep in mind this might be running on slower, older Android devices

What I'm wondering if there is some limit where the number of cards in a single application becomes cumbersome or affects performance on slow devices, and you begin to wish you had fewer cards.

[Klaus]

Hi Ervin,

I don't think that 24 cards will make any problems!
So you should do whatever is comfortable for you.

On the desktop you can "get away" with more than 5000 cards, if not too many images on them...


Best

Klaus