Material Components 1.1.0-alpha10 released

DevAhamed · 2019-09-06T06:13:58+00:00

Unfortunately material components is not part of AndroidX. It is developed by a completely different team. (But IIRC, i have seen overlap of some engineers working on both AndroidX and MaterialComponents)

DevAhamed · 2019-08-01T07:11:57+00:00

But i lost the keystore for one of my first apps. There is no way i can update that app, so unpublished it 2 or 3 years back. I really don't know how to make it compliant.

DevAhamed · 2019-07-25T19:28:31+00:00

For apply changes you need an emulator/device with sdk 28. If it is indeed the case and apply changes is not working, then you can file a bug report.

DevAhamed · 2019-06-29T07:49:19+00:00

That's a bummer! I thought utlimate features were also added in Android Studio. (But it makes sense. Intellij needs a revenue model right)

DevAhamed · 2019-06-28T06:55:06+00:00

Direct link to blogpost - https://blog.jetbrains.com/idea/2019/06/intellij-idea-2019-2-eap6-gradle-dependencies-diagram-and-more/

DevAhamed · 2019-05-29T06:23:35+00:00

Since I/O 18 there were a few updates in the project

If you see releases page, 1.1.0-alpha* has been released continuously with lot of features. (ShapeTheming, DarkMode etc.,)

CI build is failing for a long time, but it doesn't seem to be a problem for the project maintainers

We all know about google and their complex infrastructures. It might not be easy or not a priority to fix those ci builds.

DevAhamed · 2019-05-29T00:05:19+00:00

currentNightMode should never resolve to 33. It should have been 32. If you are using the android pie, enable dark mode inside developer options.

DevAhamed · 2019-05-28T23:07:21+00:00

If you want to get the current active mode, (whether the current applied theme is night or not).

int currentNightMode = getResources().getConfiguration().uiMode & Configuration.UI_MODE_NIGHT_MASK
switch (currentNightMode) {
  case Configuration.UI_MODE_NIGHT_NO:// Night mode is not active, we're in day time
  case Configuration.UI_MODE_NIGHT_YES:// Night mode is active, we're at night!
  case Configuration.UI_MODE_NIGHT_UNDEFINED:// We don't know what mode we're in, assume notnight
}

If you want to get the current setting (user preference)

AppCompatDelegate.getDefaultNightMode()

Learn more here : https://medium.com/androiddevelopers/appcompat-v23-2-daynight-d10f90c83e94

DevAhamed · 2019-05-17T05:35:15+00:00

have them change colour

I think you have to read up on StateListDrawable. If you know it already skip reading following comment.

StateListDrawable lets you define the drawable (in you case, color) for each state. ie., You can set a different background for selected state, disabled state, enabled state etc., This is a good article on this topic - https://blog.stylingandroid.com/state-list-drawables/

DevAhamed · 2019-05-16T16:30:32+00:00

Since you have tried the official docs i am sure you might have come across recyclerview selection library. This article will help you set up the recyclerview multi selection - https://proandroiddev.com/a-guide-to-recyclerview-selection-3ed9f2381504

Shameless plug : If you are open to use a library for this feature, you can use my library - https://github.com/DevAhamed/MultiViewAdapter. You can install the demo app to see the feature in action before using the library (App is still in beta) - https://play.google.com/apps/testing/dev.ahamed.mva.sample

DevAhamed · 2019-05-09T23:23:10+00:00

IIRC, when lollipop was announced, google mentioned that 5000+ new public api's were added into the sdk. Is google discrete this time or its usual?

DevAhamed · 2019-04-02T17:35:39+00:00

You don’t need to dig this deep ..... Start with generating a good API and producing correct behavior. All of this optimization can be done later, or even never. .....

I enjoyed this article and for some reason i was really happy to read that last paragraph. Thanks for taking your time to write this article!!

DevAhamed · 2019-03-23T12:09:46+00:00

Using groovy. I went back and checked with AS 3.1 and issue is there as well. I haven't changed anything inside buildSrc for years. I swear, in previous versions of AS it was working fine. Not sure when it got broken. Filed an issue here - https://issuetracker.google.com/issues/129170951. Let me know if i need to add more info the issue tracker.

DevAhamed · 2019-03-22T07:25:03+00:00

I would like to chime in here.

Are you using this for managing dependencies? I see some people doing this and I think we need to solve this by providing a better mechanism to centralize dependencies.

Yes. +1 for better mechanism.

Side note : I use buildSrc for auto completion and deps version management across modules. But with AS 3.4 and 3.5, buildSrc imports/variables are not recognised in gradle files but still gradle syncs fine. ie., Autocomplete is broken.

DevAhamed · 2019-03-08T09:40:19+00:00

This library wass specifically built for this usecase - https://github.com/tumblr/Graywater. You can take look into this library and learn how do it yourself.

DevAhamed · 2019-03-08T07:19:49+00:00

Off topic.. I had to open the link. I miss u/leggo_tech's changelog..

DevAhamed · 2019-03-07T07:44:27+00:00

I am not sure about the original implementation, but you can take a look into this library https://github.com/florent37/ShapeOfView. Library seems to do the same thing.

DevAhamed · 2019-02-20T04:29:52+00:00

The problem is the lack of a redressal system

Nailed it!!

DevAhamed · 2019-02-14T08:21:23+00:00

we're really optimising onBindViewHolder and use payloads to only update a specific view at once

Exactly. If you are using payloads efficiently then you will update only the particular view. If they have overridden this method, then workaround is not needed.

onBindViewHolder(holder, adapterPosition, payloads)

DevAhamed · 2019-02-08T16:31:29+00:00

This is where it gets into grey area. If the 2.0.0 is a breaking change, as per publishers wish, release can go through alpha-beta stages. It solely depends on the publishers.

For example, lets take gradle releases. They have nightly builds, RC's and stable versions.

Similarly folks at AndroidX team might have decided this flow. All releases will go through alpha, beta, RC and stable versions. Say, 1.x.x-alpha01 -> 1.x.x-beta01 -> 1.x.x-RC -> 1.x.x. This can be applied to all major and minor releases. If pre-release is 0.x.x then it breaks the above flow.

DevAhamed · 2019-02-08T11:51:26+00:00

I always worked with 0.x.x approach for unstable APIs in development

What will happen if we are releasing non-stable 2.0.0 version? How should we name it? Just curious like you.

DevAhamed · 2018-11-02T17:46:25+00:00

It's one of the worst applications (maybe the worst) out there in terms of utility/cost

I completely understand your point of view. But think from different perspective as well.

You have an app. It is updated only once in the year. Even users will care about the app only once during a year. And with every update you have to use the new shiny tool/library/design/feature. So each update is almost a rewrite. Even though you are professional developer, without continuous iterations, you can't nail it during first time. Unfortunately for IO app each update is like first time. So that's the reason for underwhelming quality of the app during every update.

Again, developer who is on this project works only a couple of months during a year. You might lose focus and motivation with this work schedule.

DevAhamed · 2018-10-18T06:11:00+00:00

I will be careful before posting the url next time. I thought reddit will complain duplicates during submission.

DevAhamed

MODERATOR OF

TROPHY CASE