Definitely a difference but there is a similarity in vectors of attack: The contact address book can be taken off the phone using the Apple SDK. Then, that data can be anywhere the developer wants to store it.
Apple could have a similar situation. Via the iOS SDK, developers can ask for access for a phone’s address book. These contact connections could be harvested by bad developers. They could also be sold by those developers. This is merely one example. All companies with data and APIs are vectors of attack.
Seems to me the biggest takeaway from the article was that it was Lego's partnerships that saved the company. Without those deals with Star Wars (for example), the company would have not needed to meet demands in the first place. This seems like a big lesson to learn from.
Where is native support for iOS and Android? Why do we bother generating the same assets for different screen densities? Am I the only one who wants SVGs on mobile?
As a user, having to file a form using EchoSign, I would to cringe. It requires flash and has some really bad usability. An example of that is requiring at least two non-standardized date formats. UX is important for forms because humans make errors when information is not clear.
This is obviously very cool. My one thought is that it would be very hard for children to use. It's important to consider adoption from a wide audience.
This just shows that the current state of Javascript is a confusing mess. Where do new developers start now when they are been fed ES6 transpilers and ReactJS.
I think Google (as usual) is getting ahead of this problem. But they shouldn't be alone in the fight for clarity.
Adding images makes DuckDuckGo now a legit competitor for Google for my usage. The usability has also dramatically improved as well as load times. Their mobile javascript needs to recognize gesture swiping and other minor UX improvements. But this is a leap forward for them.
Could be used for notepad API or something public. That said, it seems that services like Parse and Firebox seem more robust and also have faster response times.
The mobile ecosystem could really use a platform that is web friendlier. Firefox OS will have web developers becoming mobile developers overnight. That said, I wonder if those developers will understand the performance differences of a desktop vs a mobile device. If they don't, the performance of Firefox OS apps will be awful and Firefox will be blamed by the end user.