In order to reach higher efficiency levels whilst maintaining the quality of our work, we refine our design thinking process in retrospect with every successful project. “That interaction is interesting but I think you’re getting carried away with the tool rather than seeing the simplicity of this content layout…” “I love how your stuff looks, but I’ve built is and it just doesn’t feel right… see here when these panels move about… I lose my place” Not to say that you couldn’t do it all on your own, but we like the tension between two designers challenging each other to refine work holistically. Our approach works best with a paired designer set. We’ve taken a deliberate decision to see the strengths in each tool (Axure and Sketch) and to run streams of work that make the most of the disciplines each tool can exploit and assist. This tends to mean we are required to work collaboratively, be rationalised, documented, and efficient at scale.” “We usually work on enterprise grade UX/UI for products and platforms that are subject to continuous improvement or large corporate projects. Spoiler: we don’t… We have to run 2 streams as seperate disciplines How does EVOLVR fix the Axure-Sketch gap? But oftentimes they’re missing the value of real interaction, pivoting on ideas, and trying to disconnect from visual ( sometimes personal) ideals that emerge as an emotional investment. Already I can see Sketch users dismissing prototyping as it’s so easy to nail really nice finished visuals. The key reason for this is the lack of integration with what appears to be a rapidly evolving open market for plugins and platforms in Sketch. I get that! But I also see that as a ‘ head in the sand’ issue, and eventually, users will stop opening that box that Axure is already in. By Axure holding onto its ‘ rapid interactive prototyping’ space, it puts up a wall to others and says “ we’re the best at this and we’ll keep optimising what we’re good at”. No UI/UX product has ever really nailed all collaborative interactive design requirements. Sadly, Axure is now in a box and stays there.Īxure probably want it to be this way to an extent. my product owner needs to see this mocked up so they can grasp the concept better, or we need it so we can get more insightful user testing done. Or worse still “I’ve done some work that I really like, now how do I export it to Zeplin, or how do I get it into Sketch to polish it?”Īt this point, the user tends to fall away and shelf Axure as a great tool for specific jobs e.g. “OK, so I’ve got the hang of it, how do I import some of my Sketch assets?” Why haven’t I used this before?”īut those euphoric moments are also invariably met within days with: Invariably, they’ve all come back to me in less than 24 hours saying: I’ve introduced many newcomers to Axure over the last 2 years and some of them have been devout Sketch users. (compare that to the beauty of Adobe’s XD - a ‘Sketch rival’). That’s a shame as it puts off would-be users.
Axure has an obtuse interface that is scary to newcomers and immediately unintuitive. In 2012 I started to push out Axure work as I was more interested in directing work at a structural level than the visual design elements. No amount of Adobe’s tweaking ever moved it away from that. To be honest, Photoshop was always a hack but it became a familiar friend despite being bogged down as a photo tool. I’d tried Fireworks, Flash, and others but never really felt at home. For what seemed like a lifetime for me (1999–2014) I was a hardcore Adobe Photoshop user.
0 kommentar(er)
