Where the design community meets.
Joined over 7 years ago via an invitation from Joe S.
tom hasn't posted any stories yet.
Hey Kuldar, it's Tom from the Studio team. I'm sorry to hear that the wait has gotten to you. Our team is certainly cranking hard to get everything in tip-top shape before rolling it out to the world. You may have noticed that we've started ramping up access quite aggressively over the past week. This will continue over the next couple of weeks until all early access users have it in their hands. Building software this complex is no easy task and we feel it's really important that our first release is robust and performant enough to handle your everyday needs. We're almost there and I hope you'll stick with us!
Thanks for the question. We're working on a big leap to help manage Sketch and Photoshop files with Inspect. However, there are plenty of other ways we can improve collaboration around a file. It sounds like you may be asking for version control. Is that a fair statement?
Managing design assets has always been a tricky beast and no one has quite nailed it yet. That being said, it's certainly an area we're thinking about as more and more source files are uploaded to the platform.
Any thoughts on what you'd love to see?
Web or native is one of my favorite debates, so thanks for bringing it up!
While I don't have a hard stance on one or the other. I think that we're at an interesting point in the evolution of the browser where functionality that was typically owned by desktop software can now be reproduced in the browser. We're going to continue see desktop apps making a leap into the browser and I don't think there's anything necessarily wrong with that transition. It is my belief, however, that certain types of tools benefit most when they exist outside a standard browser.
Performance is the case usually backing native apps and it's certainly one of the most important when supporting intense, creative workflows. However, I think there are tremendous UX benefits that browser-based apps miss out on as well. If you're building an application that people need to have in front of them at random yet extensive intervals throughout their day, your software probably benefits from being on a dock. I look at the browser as a junk drawer and tabs as items in that junk drawer. I throw a ton of junk into it. So does my wife and my daughter and it all gets shuffled around over the course of weeks. Some tools work well in a junk drawer – like a bottle opener. Some tools – like my phone – do not. I need it all day, every day. My phone doesn't go in a junk drawer; it goes in my pocket for quick recall and extended use.
Most of InVision's tools are in the browser because they're centered around collaboration and encourage a rapid workflow. Ideally we get you in and out as quickly as possible, so you can get back to your day. So, I think it really boils down to how a product can you best serve its users. Sometimes things align in the browser. Other times it requires a purely native or even a hybrid solution.
With Macaw, we learned a lot about code-automation. That knowledge will certainly work its way into InVision’s products. With regards to Inspect (InVision’s upcoming code extraction tool), our efforts are currently aimed at helping developers extract code manually, which gives them exactly what they need when they need it. However, that’s just the first step. We see a lot of opportunities to help with the design to dev hand-off and we're exploring things like styles guides and automation. How far we take that really depends on user needs.
So really… What are your needs? What do you hope to see?! ;)
Hey there! I thought I'd chime in on this. Honestly, we can’t thank you enough for your support. We wanted to keep this with the community and Kickstarter gave us that ability. I personally left my job and worked without pay for a solid year before Kickstarting. The funds we received were used solely and sparingly to keep the lights on at home and food in our children’s mouthes. Without it, Macaw would have been nothing more than an idea because we had already spent our entire savings trying to build it. The wife was ready to kill me!
We were one of the few Kickstarter campaigns to actually deliver our product. We even did it on time, which is rare! We poured every piece of ourselves into what we were building and I’m quite proud of what we accomplished. Our very small team was able to build something that would have cost other teams millions of dollars and years of engineering. Not only that, we were dedicated to building more, so we started Scarlet. It's not done, but it has some amazing potential. We realized the best way to maximize that potential is with the help of someone. That someone is InVision.
Macaw only exists because we all came together to make it real. That’s awesome. This community is self-powering and we’re honored to play our part. We have a lot more coming. Thanks so much!
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.