✨✨ Preview: Jetpack Compose ✨✨

[JeelDobariya38]

Changes Made

• Improve the dependency catalog.
• Setup Jetpack Compose & Navigation 3 Dependency. (for future)
• Add Jet-pack Compose Support. (preview-mode)

Breaking Changes

• Introduce Jetpack Compose to passcodes project. this will effectively deprecate the old UI made in passcodes.

Notes

basically, setup the dependency of project for future. so that in upcoming pr's project can be migrated to jetpack compose and clean architecture. under issue #42

[razorblade23]

I am not good with android programming, but i do know that this is a step forward.
This is what is reccomend as a Android developer.

I would only suggest one change...

Dont call the oldui or newui but ui_v1 and ui_v2
That is a bit more self explanatory, as you can now have more "versions" of UI and maybe even give users option to change it (in some distant future)

[JeelDobariya38]

Dont call the oldui or newui but ui_v1 and ui_v2 That is a bit more self explanatory, as you can now have more "versions" of UI and maybe even give users option to change it (in some distant future)

Didn't think of that earlier, I have think/made the oldui and ui, the way they are, because i have initial thoughts that the new ui can be made gradually. and old ui will stil be there as kind of like, standby.. it like using a feature flag...

and once ui (jetpack compose) is made completely, I can remove package oldui.

I have seen this type of things in GitHub & Leetcode and from thier i have drown the idea of preview ui.

[JeelDobariya38]

but yup!! your idea is nice and good.. maybe after sometime when new ui is stable we can have also old ui... that user can turn on...

I think this type of version switch is necessary and feasible.. because there might elder people, I mean non younger how might have difficult in navigate new ui of android.. so yup a really good idea @razorblade23...

what are your suggestion or thought?
@kudanilll