third stage is considerably more difficult than first two stages

[RedJocker]

The third stage contains significantly more task items than the first two stages put together. I would distribute them more proportionally for a gradual increase in the complexity of the stages.

on revision by @Razotron

[RedJocker]

my thought on stages objectives was closely related to prerequisites and what I was thinking in terms of prerequisites for the first 3 stages was

• stage1 - Text composable
• stage2 - Rows and Columns (styling too, but that is part of Text although it seemed more convenient to have this at stage2, because I wanted to have the styling linked with the idea of giving visual cues on the intended structure, contrasting Title with MenuItems)
• stage3 - eventHandling with simple mutating state effects

just for completion the remaining stages thought prerequisites were

• stage4 - reusing composable to make a list
• stage5 - Button + hoisting (state and event handling) + Toast

So it is right that the complexity of third stage is higher than the first two stages due to the nature of the subject, but I don't really intend to make the first two stages more difficult. Maybe it could be that stage3 was only about incrementing and decrementing the counter with no other logic involved, and have a new stage that would be just about limiting the counter max and min values, but at this stage of the of the project I'm thinking users will probably already have dealt with many kotlin topics as to be able to handle that amount of logic.

I'm more prone to declare this as wontfix than anything else, but for now I will leave the issue open so that it can be argued against this inclination

[RazoTRON]

I think we can come back to this issue after considering other open issues.