My guess is that there's an implied "/s", since it may remind iPhone users of what App Library looks like when they tap the search bar. https://imgur.com/a/nC2R0hG
The App Library is nice because it relieves iOS users from micromanaging app grouping/arrangement. I now have just one Home Screen of widgets (including contextual Siri app suggestions), then swipe left to use App Library when needed.
We can't control the decisions they make, and wouldn't want to... Each agency has their own CIO, and needs to be able to make decisions about stacks based their needs. Compliance requirements for running a service in public are so huge that agencies have conservatively stuck to ancient options, or farmed it all out to vendors. Our goal is to make the operations, deployment, and compliance aspects of service delivery trivial so they can put more of their resources (and those of the vendors they pay) into the improvement of the services they provide rather than sinking a huge portion of their budgets into redundantly addressing compliance and deployment concerns. And of course, use modern tech.
Good luck with that. I was only a government contractor and the amount of blue badges that argue how the other agency is doing it wrong / stupid and they would never use their stack is insane.
You're right, everyone is on the hook for their own agency, and with such strict regulations they are very conservative about using each other's stuff, which is effectively delegating decisions and responsibility to others that may get them in trouble.
This is a major reason for cloud.gov going after the FedRAMP JAB P-ATO recognition. "JAB" is the Joint Authorization Board comprised of the CIOs of the Department of Defense, Department of Homeland Security, and the General Services Administration. Having a triple-sign-off from three CIOs under a consistently applied set of standards is the highest social proof you can get in government that will convince other agency CIOs that it is OK to use your stuff at their agency. Normally it's vendors that go through this program... We're among the few to do it for a government-developed-and-operated service, and the first to do it for something as generally useful as a PaaS.
The other aspect is making sure everything we do to deploy and document the platform's compliance is open source and subject to scrutiny, so they can check for themselves... and ideally contribute in areas they think it could be better, of course!
You're fighting the good fight and seems you have a good path. Curious how far you guys make it (it almost seems like everyone is against using "the other guy's" stuff but the vast majority of the time it would save millions). Good luck!
It’s a no-win situation for Americans who are forced to pay $10,000,000,000 annually to fund an agency to spy on us and find “terrorists” or $160,000,000,000 annually for wars if they don’t find actual terrorists.
Neither of those expenses has its desired outcomes, nor are they mutually exclusive.
When I moved to SF I knew next to nobody. I worked freelance at a coworking place and went to hackathons. Most of my SF friends are from these social environments.
Typography is pretty awful on Android in general. Both Roboto and Droid Sans are nightmare Frankenfonts.
Font rendering on Android is bulky, blocky, and fails to consider how humans read letterforms. So, even if a designer can convince the team to license a better font, it’ll end up a smeared mess on users’ screens.
The API calls to layout type on Android suck. (iOS sucks slightly less depending on how willing your UI engineer is willing to devote to this most basic foundation of design.)
“U MAD, BRO?”
Yeah. I get paid to be a picky snob about what the user sees and how they feel about the product. It pisses me off to look at Android because its not disappointing, the way Win8 is, but actively anti-design. Why pay to license good fonts? Why make a system for rendering type nicely? Because this stuff is basic user experience. It's like going into a hotel and discovering that the paint is yellowing. That hotel is more likely to have dirty towels, no hot water, smelly sheets, and bed bugs.
> Typography is pretty awful on Android in general. Both Roboto and Droid Sans are nightmare Frankenfonts.
I like Roboto, but what do you find to be bad about those fonts?
> Font rendering on Android is bulky, blocky, and fails to consider how humans read letterforms. So, even if a designer can convince the team to license a better font, it’ll end up a smeared mess on users’ screens.
This isn't really true when setting custom typefaces on various views. Just subclass them and set up the typeface in the constructor and you are done. You just end up using that subclass your in layouts instead of a standard TextView.
> It pisses me off to look at Android because its not disappointing, the way Win8 is, but actively anti-design.
I'm not really sure what you mean w.r.t to text. The text views and code cover most use cases and offer ways to handle flowing text in some cases, but you can always fall back to WebView rendering text content (which is easier for writers or editors to handle when making the text content).
Isn't it only a problem for fonts without subpixel hinting? I've used a fair amount of custom fonts, most render perfectly fine, and looking at well-designed apps I never felt like it's an issue.
Trickle down compensation, already.