Why isnt M2 getting new feature updates like date ...
# compose
m
Why isnt M2 getting new feature updates like date dialog and time pickers. It is hard enough to migrate an app to compose. Now, i need to migrate to M3 too because some components do not exist in M2 but do in M3 :0 android dev is hard
a
For the most part, you can probably copy paste the M3 component and adapt it to M2
Compose is open source, nothing is stopping you to go on to Android code search and find the component to reuse
m
Indeed. I can also use swift to develop android apps, but that wouldnt help me, would it?
a
All I'm saying, is you have the source code available so you can backport it to material 2
s
You can use the m3 component but with an adapted m2 color scheme. It's kinda what we've done on our project with a mapping that just looked something like this. https://github.com/HedvigInsurance/android/blob/develop/app/core/design-system/README.md But after that first step, we're trying to adopt more of the m3 stuff
a
Instead of forward porting your app to material 3
Or that solution works too, compose gives you a lots of options
The inflexibility here is self-imposed, sometimes app dev requires work in general
s
But in any way, I agree with Andrew, you got a bunch of options. Can also use a normal view dialog for it, nothing stops that either.
a
It's just the way it is
Hell, the view system dialog works too!
I completely forgot about that 😝
Or even any other date picker dialog impl would work too
m
Ya, it is using the legacy one already. I just want to get rid of all view stuff oO
a
Welp, you have options depending on how much elbow grease you put in
Sometimes more effort is going to be required, that's app development in general. The availability of a certain component isn't a reflection of the effort put in by the teams who provide the product, nor of the solution in general 🤷🏻‍♂️
c
The date and time pickers are far from "finished" in Material3 fwiw