You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recommend utilizing the separate layers and creating two ui versions: The XML existing one and a new compose one. The main activity shows a button to go for each.
I think this will showcase the real power of separation of concerns.
The text was updated successfully, but these errors were encountered:
Well, I don't mean separate branches, I mean like in the same app. Imigain a main activity with btn for each ui way of implemenation. I don't mind separate branches, just with separate branches we'll not need the Navigation library, so we'll use the chance to demonstrate it. : )
I'm just thinking out loud, feel free to share what you think. :)
I recommend utilizing the separate layers and creating two ui versions: The XML existing one and a new compose one. The main activity shows a button to go for each.
I think this will showcase the real power of separation of concerns.
The text was updated successfully, but these errors were encountered: