IOS-10800 Make ViewStates component in SwiftUI

[alejandroruizponce]

🎟️ Jira ticket

https://jira.tid.es/browse/IOS-10800

🥅 What's the goal?

As a performance objective to make SwiftUI components, ViewStates component will be migrated from UIKit to SwiftUI.

🚧 How do we do it?

A new component similar to the component in UIKit has been created and added inside the Catalog.

🧪 How can I verify this?

FOR DESIGN MEMBER (@AnaMontes11) : There is a difference between the buttons we have for SwiftUI and the UIKit buttons, I'm not clear which one should be the correct one since I can't find references to the Design of this component. I hope that in the revision of this PR a member of Design can clarify it.

If the SwiftUI design is correct, it could be used as a base and apply in UIKit a wrapper that encapsulates the SwiftUI design to use the same design in all platforms.

SwiftUI	UIKit

🏑 AppCenter build

[AnaMontes11]

Hi @alejandroruizponce ,
Here’s the link to the button component specifications from Mística: Buttons component Specs.
You can review it to clarify any doubts and make the necessary adjustments.
Let me know if this helps or if you need anything else. :)

[DavidMarinCalleja]

There would be a missing test for this component, wouldn't there?

[alejandroruizponce]

Hi @alejandroruizponce , Here’s the link to the button component specifications from Mística: Buttons component Specs. You can review it to clarify any doubts and make the necessary adjustments. Let me know if this helps or if you need anything else. :)

Thanks @AnaMontes11, but really my question is more about what type of button is correct for this View State component. If the one we use in UIKit or the SwiftUI one, or if both are valid.

[alejandroruizponce]

There would be a missing test for this component, wouldn't there?

There were no tests for the component in UIKit either, if I can I will check and add some.

[AnaMontes11]

Hi @alejandroruizponce, this is not a Mística component; I understand it comes from an old View State. On our side, it doesn’t matter if you use a small or large button, although for consistency, it’s better to use the same one in both. If this decision is relevant for Novum or could affect something in production, we’d need to discuss it with the product team. Let me know if I’ve clarified your question.

[AnaMontes11]

Hello again, @alejandroruizponce As I mentioned, it seems like an older empty state. If it helps, I would use the same (large) button in the SwiftUI version for consistency and discuss with the team updating both to something closer to a more modern empty state.

[alejandroruizponce]

Hello again, @alejandroruizponce As I mentioned, it seems like an older empty state. If it helps, I would use the same (large) button in the SwiftUI version for consistency and discuss with the team updating both to something closer to a more modern empty state.

Talked with @AnaMontes11 and @aweell, same large button will be used on both platforms even though they are different right now. The unification of the button can be looked at in a different ticket as well as the update of the texts:
https://jira.tid.es/browse/IOS-10849

[tuentisre]

🎉 This PR is included in version 33.7.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀