Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating multiple ui implementation (branch for xml, anthor for Jetpack compose) #36

Open
AbdAllahAbdElFattah13 opened this issue Jul 30, 2022 · 3 comments
Labels
💡Suggestion💡 New idea to be implemented, improvments and updates

Comments

@AbdAllahAbdElFattah13
Copy link
Collaborator

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.

@AbdAllahAbdElFattah13
Copy link
Collaborator Author

see #34

@AbdAllahAbdElFattah13
Copy link
Collaborator Author

We can also demonstrate the Navigation library, it will be a nice addition and should ease the flow.

@ahmedeltaher ahmedeltaher added the 💡Suggestion💡 New idea to be implemented, improvments and updates label Jul 31, 2022
@ahmedeltaher ahmedeltaher changed the title Creating multiple ui implementation Creating multiple ui implementation (branch for xml, anthor for Jetpack compose) Jul 31, 2022
@AbdAllahAbdElFattah13
Copy link
Collaborator Author

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. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💡Suggestion💡 New idea to be implemented, improvments and updates
Projects
None yet
Development

No branches or pull requests

2 participants