Wireflow – free, online, open source tool for creating user-flow prototypes
wireflow.co
wireflow.co
2. Then there was a rewrite with React, but not yet a way to save data.
3. Then maintainers did have some other projects where they did spend most of their time.
That brings my questions, are some interested in this kind of tool? Would some like to contribute more to Wireflow? Has some news about other similar tools bring more interest to have Wireflow maintained even better?
Just thinking, as one of the maintainers of Wireflow.
Friendly maintainers but I think being built by an App development studio, I can imagine they have different priorities.
Zslot has put an incredible amount of work into it and it extends excalidraw to have a lot of additional capabilities. You can also use it within Obsidian canvas for some of the flow stuff you mention but you could very likely just use the plugin.
Zslot is constantly updating it too so you get new features and updates almost every other time you open it. Amazing work done there.
And Obsidian is just awesome too :)
Meteor has very active development. I have used Meteor for many years.
But what do you mean by drawing? Are there supposed to be drawing tools?
It looks like bunch of templates for constructing site-maps?
Is this supposed to encompass mobile design patterns as well?
I understand it was done in less than a month but if you take a few days to learn something like Principle (https://principle.app/) then you could the rest of the work in two weeks and have an interactive full scale prototype in at the end.
I'm not sure what I expected trying to check it out on my phone, but I'd at least expect to be able to run it on a tablet. The use case for running it on a phone might be to view, but not edit a project. One might need to review changes and reply to an email chain or teams chat between meetings from their phone if this was going to be used in the real world. Would suck to need to juggle nth-revision PDF exports about an app design. Everyone hates that.
I eventually want to incorporate something like this in my tiny ux app (https://www.tinyux.app), but have not yet gotten around to it.
It would be so cool if you could start either from the flow, page or component perspective, but all are essentially using the same source of truth.
Had a presentation once to a room of UX designers who really liked the vision and concept. Then I showed them my prototype with vim-like text commands to manipulate wireframes and got a lot of blank stares. Still makes me laugh to think about that mismatch of expectations.
So this looks like a sitemap.
Is that all?
E.g. Login Form. Could should initial state -> error state -> submitting state -> success state. Could be a "User Login flow".
Not to be the grammar tsar, but if anyone from there is reading this it could do with a little fixing.
Any recommendations?
https://gitlab.com/saxion.nl/42/wiretext-code#wiretext-vscod...
A (non-text-based) alternative I kind of like is Quant-UX: https://quant-ux.com/
Love the indentation based DSL - this looks very intuitive.
I do a lot of quick sketches with excalidraw but I easily see wiretext-code replacing that with a better workflow where I can extract out components and prototype by composing those instead of copy pasting around.
> mockup does not quite get us there (not sure why)
I can only speak as a dev, but it's incredibly frustrating when design agencies leave out too many details or don't consistently follow guidelines. No tool is going to fix that.
On my side of the fence we generally don't care about the tools used as long as we have a completed design to look at that isn't late and isn't going to be pulled out from under us. I've seen product managers lie about all reviews being completed to "get devs started early" only to see the next revision break a ton of work. They also lie about copy text being final not realizing the impact even one word can have on everything. I've seen designers commit sins ranging from using system or licensed fonts causing them to have to rework an entire layout to not even exporting assets properly or at all before handing off to devs. If you have people like that, the back and forth and pain is endless for everyone.