4 ms·
"Faster in the cloud With Figma, your files just live on the Web. No more version mixups. No more cloud syncing. No more transferring files between your work an
by croes 4y ago
"Faster in the cloud
With Figma, your files just live on the Web. No more version mixups. No more cloud syncing. No more transferring files between your work and personal computers."
In other words, your data doesn't belong to you. No service, no data.
There is no cloud just other people's computer.
- pavlov 4y agoAnd this is why Adobe is paying so much for Figma: they’ve built the kind of closed data garden that Adobe wants to own across its whole product range. Every year it becomes a bit harder to find the “default to local file system” setting in Photoshop (it’s off on a fresh install). Every year the UI for Creative Cloud files becomes a bit bigger. Eventually access to local files is probably going to be locked behind an administrator password with scary warning dialogs.
- 7952 4y agoExactly. They want to be the Microsoft teams of media. The individual apps are less important than the ecosystem and network effects.
- de_keyboard 4y agoI hate it but will probably pick up some stock.
- eurasiantiger 4y agoYou are an enabler. Are you not ashamed of your choices?
- glenneroo 4y agoYou can't even disable it completely, at best in e.g. Lightroom you can pause the cloud sync and it may get re-enabled without your consent. You will only notice that your upload bandwidth is suddenly saturated and if you have a monitoring tool installed, are you able to determine who is the culprit. It once chewed through my meager monthly quota overnight when I installed it on a laptop prior to going to a friend's house who didn't have internet while tethered to my phone. I was very unhappy about that "feature" to say the least.
- leokennis 4y agoWhy not build a reverse cloud solution? Files are worked on right in the cloud, and then afterwards automatically synced to a local folder on one or more computers? This way if the cloud implodes, you at least have several (nearly) up to date copies of your work.
- rubatuga 4y agocough cough git
- mattkevan 4y agoAxure, another design and prototyping tool, uses a Subversion-style model, where you have both a cloud and local copy. You pull down the initial file, save it locally, then check out individual pages or components to work on before pushing them back up. It means you have to manually manage the commit state which is a bit of a pain, but it’s good because you still have the file and can work on it if you can’t access the cloud for whatever reason.
- kwijibob 4y agoSure there are risks- but it is fantastic functionality to collaborate in a web first app like Figma or Google Workspace.
- matsemann 4y agoIf you've ever tried collaborating on design files, the file only living on the web is a feature. No merge conflicts or other issues. No sending the same file back and forth with new revisions. Abstract for Sketch is nice, but having to help a designer resolve merge conflicts is annoying.
- hsn915 4y agoIf you're a company, this is solvable by making the files live in a server the company controls. If you're an individual this is obviously not a concern.
- mavhc 4y agoCan multiple people edit the file at the same time then?
- jasode 4y ago>If you're a company, this is solvable by making the files live in a server the company controls. A company policy blessed shared folder on a file server still doesn't solve the "Single Source Of Truth" issue. That's why corporate servers still don't stop the proliferation of files such as: budget2022_v2.xlsx budget2022_v3_draft.xlsx budget2022_v15_revised_by_JaneDoe.xlsx ... etc ... So one way corporations try to solve that is using groupware/collaboration software such as MS Sharepoint. Users are then supposed to "check out" the xlsx file and then check it back into the "document library". But the process is so cumbersome that very few companies and users have 100% discipline to do that. This also doesn't let multiple users edit at the same time. The new generation of cloud-first-collaboration-as-1st-class-UI services (like Figma) don't have the multiple conflicting docx/xlsx issue because sharing the work is the baseline normal usage. Figma doesn't try to bolt on the collaboration behavior to 30-year old software and file formats like MS Office.
- hsn915 4y agoYou're thinking in terms of badly designed technologies you are familiar with. I'm talking just about a solution to the problem at hand: Instead of storing files on servers controlled by a 3rd party company (and calling it "the cloud"), you store the files on servers that you control (and don't call it the cloud). I didn't say anything about share point or how the files are to be stored. This can be a feature builtin to figma or any application that is "cloud native": all you need to configure is the server address.