

0 / 2 embers
0 / 3000 xp
click for more info
Complete a lesson to start your streak
click for more info
Difficulty: 3
click for more info
No active XP Potion
Accept a Quest
Login to submit answers
With Tubely, we have it easy. Users won't be able to make small tweaks to existing images and videos - like changing the background color or adding a text overlay.
We'll force them to simply upload new versions of the file (even YouTube has this restriction, even with their resources).
If a user were able to live edit a file (think Google Docs or Canva) we'd have to approach our storage problem differently. We wouldn't just be managing new versions of "static" files, we would need to handle every tiny edit (keystroke) and sync updated changes to our server. That's much more complicated and outside the scope of this course.
Luckily, those requirements are also less common in the real world. The Tubely use case (storing and serving entire assets) is much more common and much easier to implement.
What makes live editing (like Google Docs or Canva) more complex than static file uploads?