5 ms·
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
by pavlov 10y ago
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. It's like trying to produce a movie by doing color correction before you even have a screenplay.
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. This tends to lead to usability problems down the road, when users discover those "dead ends" that the design unconsciously avoided.
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. 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.
Companies 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.
- vvanders 10y ago> 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. 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. Yup, that's why I feel it's super important that these type of tools feed into a production workflow. It means you can hit those constraints upfront(removing needless back and forth between eng<->design) and you as a developer don't have to worry about pixel minutia. It's a win-win on both sides, but a really hard sell since the impact is a second-order effect reflected in the work produced instead of the tool its self.
- darknoon 10y agoOrigami eng here. I agree completely: the defaults should be the platform conventions. 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. You can show an iOS styled Action Sheet, Android checkbox, etc., without building it from scratch (look in the layer + menu). 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. 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. You can also break these components open and customize them, somewhat like you would as an engineer by subclassing or composing sub-parts. Internally at FB, we also made some custom layer patches that match the UI conventions for the FB app, Instagram, etc so you can have consistency by default. These bundles of layers & patches are called Systems (still working on docs for this), which you can build and distribute among your team. There is some more about this in our F8 presentation earlier this year. The idea is that as a designer you can fill in the text for your Alert View or whatever instead of messing around with resizing rounded rectangles & text boxes like in Sketch.
- theschwa 10y agoI've generally seen tools like Balsamiq and Invision used for the app flow and tools like Framer and Origami used for micro-interactions. I would, however, like to see something that blends the two well, but maybe that just doesn't fit with enough people's use cases.
- mortenjorck 10y agoWhere I work, our solution to at least part of this has been to keep a tight feedback loop between design prototypes and developers: We make it a habit to get engineering eyes on things early on, so we can ask, "can we do this easily? Does Android support this natively? Will this trigger a big refactor somewhere else?" To your movie analogy, I'd compare tools like Invision to scriptwriting and storyboards, and tools like Origami to animatics and previsualization.
- spanktheuser 10y agoExactly this. There are countless tools for flows and storyboards. Origami and others are competing to be the photoshop of software interface design. Exploring animations, visualizations, events and movement with speed isn't a solved problem yet. Which is probably why these things are emphasized in the marketing for the tool.
- pjc50 10y agoThis is a strong argument for prototyping the workflow with index cards and pen; deliberately rough to deter people discussing whether it should be cornflower blue. (I think there was a tool that offered this, XKCD style, but I've no idea what it was called)
- taco_emoji 10y agoBalsamiq? I'm sure there's others that do that too...
- kirushik 10y agoEvolus Pencil has a stencil library like this (called SketchyGUI). The tool is also cross-platform and free (as in freedom).
- JonathonW 10y agoThe last iOS UI I did prototyping work on was done using PowerPoint using a set of sketch-styled components (from this[1] guy, although I can't find the particular set that I used on his site right now). Mostly worked out pretty nicely and avoided the inevitable digressions into "what shade of puce should the title bar be", but there is no way to adequately express on Hacker News the facepalm I made when someone complained that the sketch/wireframe style wasn't going to work too well for the finished app. [1] http://keynotopia.com/ http://keynotopia.com/
- randartie 10y agoWouldn't the type of prototype created in origami be past the index card stage, and should be the time to think of things like that?
- bbcbasic 10y agoI agree strongly so I submitted that idea to HN :-) https://news.ycombinator.com/item?id=12811708 https://news.ycombinator.com/item?id=12811708
- GuiA 10y agoLow fidelity prototyping is indeed a fantastic tool! It can also go way beyond index cards. See for instance http://prototyping.club http://prototyping.club
- gk3 10y agoisnt this more the fault of the designer and not the tool?
- pavlov 10y agoIt's more like a warning against getting carried away with the latest tool. It happens easily to developers too, after all (hello useless rewrite in latest JS framework). Origami is excellent and parametrized animations can be actually useful, it's just not so widely applicable or foundational as some designers and project managers think.
- lj3 10y agoJust out of curiosity, what do you think about this tool: https://www.kickstarter.com/projects/298226251/subform-a-modern-tool-for-digital-product-designer https://www.kickstarter.com/projects/298226251/subform-a-mod...