Where the design community meets.
Ux/Ui designer and front end developer Joined almost 2 years ago
Absolutely agree... Inbox is amazing. I see a lot of people referencing bugs—in my experience I haven't come across any
Another point—I assume it would cost a lot more to store design file blob data than it would to store txt files (in the case of most programming languages).
It feels like Adobe is on its last legs... That being said I'm probably bias as I have little need to go near their products since graduating and progressing on to full time digital product dev. Still I can't believe how late they were to the prototyping arms race.
Works on my machine
Yeah, the hype around figma seems to be getting bigger and bigger everyday. I haven't tried it properly yet...
I do like the idea of a cross operating system design tool...
What's it like in terms of open source plugins? Does it support community development/does it have a strong community behind it?
Abstract is great. It is still early days in terms of design version control software, but I think Abstract is probably the industry leader. They have good customer support and are very quick to respond (they issue fortnightly patches with fixes addressing any bugs raised by the community)
Tbh I haven't come across any major bugs and I've been using it since release. The one downside is its a bit of a ram hog, so if your project is large and you're running other programs/multi-tasking it can slow everything down significantly... It's getting more and more optimised every week though.
Another thing I'll mention is that there is a bit of a learning curve, particularly if you don't have any development/git experience. To get the most out of version control designers have to reframe their process a little bit. Instead of just opening a sketch file to work and incrementing your files each iteration, you kind of have to think in terms of designing, committing and merging by feature. This change will slow you down at first but it's for the better as your design history will be modular and organised so you can go back at any stage and re-implement changes or review certain stages of the design easily and of course it allows for multiple designers to be working on the same file/page at the same time with no conflicts. (Planning your commits becomes even more important when you're working with a design library as every change needs to be merged before it becomes available)
I'd highly recommend it IF you work with a team of designers. It's not as necessary if you're the sole designer... I'd probably still use it on my own simply because I like having my design history stored and sorted perfectly.
Ahhh, thanks so much for testing this for me. I guess that identifies where the issue is. Hopefully we see a resolution soon.
lol wtf... We literally just had a reply from inVision stating:
"Apologies for the trouble renaming your artboards. inVision will only replace screens with the exact same name automatically, so in order to get your screens to replace each other, we'll first need to manually replace all of the screens in Invision, then automatic syncing will resume as normal.
That said, to have the ability to rename a screen but still maintain the connection to the screen within the InVision prototype for updates is a potential feature that our product team is tracking. They're monitoring interest and reviewing whether we should add this functionality to our product."
So they don't support it? The Craft by InVision support page says they do... I guess they don't consider Craft a part of their product
Wow really? Maybe I'm experiencing some kind of bug...
Are there multiple designers working on the same project in your case?
ur edgy for calling it edgy eksdee
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.