11–20 of 22 posts
This sounds just a lot my systems analysis and design classes years ago (waterfall days). Who would think of gathering requirements and specs in these days of Agile....
And Facebook showed clearly that you can change your API daily and no one cares.
For everyone else, we have to provide good experiences with stable products.
This sounds just a lot my systems analysis and design classes years ago (waterfall days). Who would think of gathering requirements and specs in these days of Agile....
And Facebook showed clearly that you can change your API daily and no one cares.
I think Android could have been much better if these principles were taken to heart during the design of the main APIs. From what I recall Josh collaborated with the Android team at some point; sadly too little too late. IMHO almost every Android API i use violates some principle in this presentation.
iOS and Windows APIs are so much better.
I think it's fair to assume that most people share the same experience.
I think Android could have been much better if these principles were taken to heart during the design of the main APIs. From what I recall Josh collaborated with the Android team at some point; sadly too little too late. IMHO almost every Android API i use violates some principle in this presentation.
More seriously, every sufficiently complex, real-life design I have ever seen has been a set of compromises to best meet a set of competing constraints. The most that I hope that a book or a lecture can do is provide a general set of principles that an engineer should consider, and be mindful of they are going to violate them. I can't think of any very complex platform that hasn't run into this issue, and Android is no different, and probably fares better than most. Do you have any examples that you would prefer instead?
I think Android could have been much better if these principles were taken to heart during the design of the main APIs. From what I recall Josh collaborated with the Android team at some point; sadly too little too late. IMHO almost every Android API i use violates some principle in this presentation.
My response (in good humor of course): https://cdn.meme.am/instances/500x/45999359.jpg More seriously, every sufficiently complex, real-life design I have ever seen has been a set of compromises to best meet a set of competing constraints. The most that I hope that a book or a lecture can do is provide a general set of principles that an engineer should consider, and be mindful of they are going to violate them. I ca…
I think the difference is that Apple had decades of institutional GUI expertise. Android engineers were more like hardware/OS guys as far as I can tell, and perhaps less experienced with the abstractions conducive to easily creating nice GUIs.
Earlier quoted context omitted.
My response (in good humor of course): https://cdn.meme.am/instances/500x/45999359.jpg More seriously, every sufficiently complex, real-life design I have ever seen has been a set of compromises to best meet a set of competing constraints. The most that I hope that a book or a lecture can do is provide a general set of principles that an engineer should consider, and be mindful of they are going to violate them. I ca…
Uh, isn't the obvious comparison iOS? I think the difference is that Apple had decades of institutional GUI expertise. Android engineers were more like hardware/OS guys as far as I can tell, and perhaps less experienced with the abstractions conducive to easily creating nice GUIs.
And people say there's nothing copyrightable in an API design...
Just because something is a creative act doesn't mean it's covered by copyright. If your functional creation is useful and novel, get a patent on it.
Someone should add (2007) to the title.
Someone at your service. Kind of interesting that this was posted 15 times and never really discussed: https://hn.algolia.com/?query=How%20To%20Design%20A%20Good%2...
