3 ms·
For what it's worth, I really think it damages the ecosystem when apps fake standard SDK classes and make them do strange things, like what Instagr.am is doing.
by pothibo 16y ago
For what it's worth, I really think it damages the ecosystem when apps fake standard SDK classes and make them do strange things, like what Instagr.am is doing. Those standard classes are there and have limitations for a reason.
I really don't like what instagr.am has done to the UINavigationBar and there's a lot of applications out there that tries to hijack known standards to make them crazy stuff.
- uptown 16y agoI like to think that its a decision that self-moderates. If its an improvement, it contributes to the success of the app and it may persist. If not, it may contribute to the failure of the app and will eventually disappear. We're so early in the evolution of mobile/touch-based applications, and personally I welcome developers trying new things and stretching the boundaries to see where there's room for improvement.
- pothibo 16y agoI agree. It's just that for most cases, it's not a matter of improving. It's a matter of being stubborn about your own idea. Look at twitter's app for example, they keep their design very close to the standard UIKit's HIG while improving some aspects(pull to refresh is a great example)