5 ms·
> Upgrades for the sake of it > Material 2 was deprecated for Material 3. No clear migration guide was provided. I tried to upgrade Why would you do that? Thi
by eviks 1y ago
> Upgrades for the sake of it
> Material 2 was deprecated for Material 3. No clear migration guide was provided. I tried to upgrade
Why would you do that? This is a self-inflicted wound that exactly matches the title. This isn't like another example of some important system library you need that gets removed, forcing changes
> Crucial third-party libraries have been deprecated
Since you've used them at this state for the whole of app's existence, you can continue to do so without any extra maintenance?
I mean, if you view any non-breaking changes as breaking, especially when it comes to UI, the amount of maintenance is infinite anywhere.
- ashishb 1y ago> Since you've used them at this state for the whole of app's existence, you can continue to do so without any extra maintenance? Well, not, for example, "OkHttp 4.12.0 does not support Happy Eyeballs which is a major issue with IPv6 networks".
- ashishb 1y ago> Why would you do that? This is a self-inflicted wound that exactly matches the title. This isn't like another example of some important system library you need that gets removed, forcing changes As I mentioned elsewhere in the article, each library supports a certain version of Android; your old library will not support newer versions. E.g. API 33 onwards there is an edge-to-edge display, and older UI libraries won't be able to handle it.
- izacus 1y agoOlder UI libraries handle it just fine and there's no need to migrate Material at all. Really, material doesn't have anything to do with edge2edge.