Hacker News new | ask | show | jobs
by hadrien01 4038 days ago
> Android Design Support Library - Making Material design apps gets even easier with the new Android Design support library. We have packaged a set a key design components (e.g floating action button, snackbar, navigation view, motion enabled Toolbars) [...]

Finally! I had to start developing for Android not too long ago, and I couldn't stand seeing "mandatory" material components for certain usages that weren't supported in the official SDK.
1 comments
krschultz 4038 days ago
Nothing is mandatory. Material guidelines are a suggestion and a set of tools to make the baseline app better by default.

In general the UI components are moving out of the SDK into the support libs or the community at large. RecyclerView & Toolbar are examples of Google untangling the foundation from the look & feel, and letting the community come up with the final implementation of things.

link
dharma1 4038 days ago
Is that a deliberate strategy or a lack of communication between teams at Google to create the SDK level support for components their design team designs?
link
izacus 4037 days ago
I don't understand this sentiment, why do you need those components? There's bunch of 3rd party libraries to implement the UI patterns. Do you go annoy Safari/Chrome/Firefox developers that they don't provide you with components for carousels in browsers as well?
link
dharma1 4037 days ago
Annoy? I'm not sure I understand that sentiment.

I think the comparison between operating systems and browsers is apples (no pun) and oranges. Browsers generally don't implement any specific UI design language, whereas operating systems do.

Android is a system where Google controls most of the baseline UI and does implement much of the Material design language in the SDK- but at least on the launch of 5.0 several components were missing. As you rightly say the community came to the rescue and there are several versions of each component now on github.

Was just wondering if that was on purpose, and the strategy is only to provide base components in the SDK, and only visual designs of a more comprehensive set of UI components - and then let the community implement the missing components outlined in the design guidelines? Not saying that's a bad thing, just curious if it's done on purpose.

link