Facebook origami studio github movie#

As much as possible, I tried to make the Ports on the layers match the API that the engineer sees in ObjC or Java so it feels like you're speaking the same language. While this doesn't include everything you need to know about iOS or Android conventions as a designer, it does encourage people to start with the standard controls and then look to custom solutions only when they don't fit. You can show an iOS styled Action Sheet, Android checkbox, etc., without building it from scratch (look in the layer + menu).

This wasn't much a part of the original Origami, but we've tried to improve that in the new version by providing some premade iOS and Android components for the most common things.

I agree completely: the defaults should be the platform conventions. Implementing all those fancy little triggered animations takes so much time that no one has time to peek at the iOS guidelines and notice how the design actually breaks 80% of Apple's rules.Ĭompanies like Facebook have enough resources and actual UX competence to get these things right (eventually), but I've seen this happen too many times at smaller agencies and startups. It's also frustrating for programmers when you are handed a high-gloss prototype that has no relation to the actual platform UI classes and guidelines. This tends to lead to usability problems down the road, when users discover those 'dead ends' that the design unconsciously avoided. The mobile previews from Origami-like tools will show a refined 'golden path' through the app with beautiful stock photos in every screen, but more boring use cases tend to be ignored.

Facebook origami studio github movie#

It's like trying to produce a movie by doing color correction before you even have a screenplay. The thing I dislike about most prototyping tools - and Origami is no exception - is how so much emphasis is placed on polishing micro-interactions before the app flow is even in place.