Hi, we are a team of UX designers that works with MacBooks and while Indigo.Design Desktop can be run on a pre-Catalina macOS or in a VM, it's really not a viable option right now, because:
This takes me to the question of IF (i hope so, given Silverlight being EOLed even on Windows) you plan to release a new version that would use different technology. And more importantly – WHEN?
Hi.
I agree that using a VM or holding back your mac versions are not viable options. Unfortunately, we won't be able to update the desktop app to run on Catalina due to deep platform changes introduced by OS X w.r.t. 32-bit apps. It's out our control, and feel helpless in that regard. It was never our intention to disrupt your work.
To answer your other question-- yes, we are working on a different design tool, This will run directly in your browser and will allow you to create designs from scratch using a consistent design language (using real UI components). With this new effort, we are aiming to provide a high degree of reuse when it you are ready to implement your designs. This tool is focused on higher fidelity designs and code generation, and not state-based prototyping features currently available in the desktop app. We are hoping to preview this tool very soon to get early feedback and match your usage scenarios.
If possible, can you share some examples of designs you are creating for your development team? I can take a look and tell you whether our new tool will fit your needs. You can email us at indigo@infragistics.com to share privately.
Assuming you are using Sketch to create your designs, have you explored publishing it directly to the cloud using Indigo.Design plugin for Sketch? Or are you referring to exporting from Sketch and editing the flows in the desktop app?
Hello George,
thank you for your reply. Finally got through to reply to you (that post-it TODO stuck to my monitor for the whole time can finally go rest in the bin)
For what we're creating in our agency, Indigo.Desktop was always a good way to get interactive results out quickly.
We aren't usually doing final visuals (we leave that to others) but rather prototypes that validate basic assumptions by materializing them so they're testable.
You can see an example what we've done here https://cloud.indigo.design/share/run/du86bkx6g95f
This one was handed over to developers as the prescribed behavior. The visuals were then added by another colleague but weren't incorporated into the prototype.
As we are not "UX/UI" (or any of the visual designers with "an eye for usability") but rather interaction designers (in the original sense of the word that Alan Cooper had in mind), visual fidelity or real UI components are not what we are looking for. And being able to use the "inheritance" that came from using states in the UI was great.
Being an ex-developer (it's been more than 14 years since I ended that career), I don't mind to get my hands dirty with code to make my prototypes move. Not sure about other people on my team.
I'd prefer using one tool in a VM using Parallels (went this way and it's quite ok, surprisingly) rather than having a multi-tool workflow.
Take care,
Petr