(Irony: the track Not In Love was playing as I typed this.)
(Lots more good stuff in the comment thread on that post, too)
sigh No, it did not.
Android started it on modern smart phones, with the original Droid that was 240dpi, and the platform itself introduced the robust multi-density support we have today a bit before that in 1.6, including full support for retina class and the ever increasing densities we see today.
But you know what? It doesn't make sense to say that Android started this, either. In fact Android from the start had core support for multiple display densities (through the dp units and such), but this happened because of previous experience at PalmSource where Palm devices had already experienced increases in display density, going from the original ~80dpi screen to high resolution 160dpi screens, and then trying to deal with 120dpi screens to be able to use then pervasive 240x320 panels.
The troubles of that last step -- trying to implement 1.5x scaling on a system where apps are using absolute layout of UI elements in pixel coordinates and the resulting strange rounding artifacts -- is a major element of what drove Android's original design. To be able to do non-integral scalings well, Android relies on layout managers to do final placement of UI elements, which run at the native screen resolution. The use of layout managers not only makes it a lot easier for applications to adjust to different screen sizes, but also allows scaling screen density by non-integral amounts without causing odd spacing between interface elements or having to use sub-pixel positioning of all elements and the resulting anti-aliasing artifacts.
In addition to the attached image, I've also got an SVG: http://staticfree.info/~steve/complete_android_fragment_lifecycle.svg which is suitable for printing.
If this is missing lifecycle steps or is inaccurate in any way, let me know so I can update it!
Dan has a great talent for relaying insight on "why things are the way they are" from his perspective as one of the folks that helps shape the UX of Android. I'm really looking forward to the next time they bring him on the podcast.
Now, with more exclamation points!!!
That's true, if by "without problems" you mean "without halting execution, permitting the program to continue under unexpected, uncontrolled conditions, resulting in god knows what kind of side effects."
I've been using a secure but awkward method for maintaining different passwords for all my online accounts, but after Heartbleed is making me change them all (😈), I've decided to give up and use something like 1Password or LastPass.
To anyone using a sync'd password manager:
1. what are you using?
2. what's good about it?
3. what sucks about it?
For the love of god, stop re-electing Dianne Feinstein.
And both Pizza Hut AND Domino's has Hot Dog Crust (Ugh!): http://foodlegend.tumblr.com/post/45206550287/dominos-hot-dog-stuffed-crust-fats-dominos
- Code42Software Engineer, 2010 - present
- Target Corporation
Required* reading: http://www.merlinmann.com/better
* Well, not "required" obviously, but theoretically you're reading this to find out about me -- here's something that'll tell you a _lot_ about me, if you're paying a little attention. Otherwise, why are you reading this? Go do something you love!
Samsung's real challenge: developing a sense of focus, taste, and restraint
Samsung's Android devices may sell well, but commercial success and optimal user experience don't automatically go hand in hand.