With modern HDPI screens, even a small photo thumbnail is often 50KB or more. The second size challenge is the photos themselves.
GOGL EPHOTOS FULL
Sending even minimal information (the photo urls, width, height, and timestamps) is many megabytes of data for a full collection, this would directly run counter to our goal of near-instant loading. The first size challenge is that for users with large photo collections (and some users have over a quarter-million photos uploaded) there is simply too much metadata. The two biggest challenges both come down to size. Here is a technical write up about how we solved those challenges, and a peek under the hood of how the web version of Google Photos works. While many other galleries now support some of these features they usually square crop each photo to make the layout work. We wanted to try something ambitious and simultaneously support a full-width ( justified) layout, preserve the aspect–ratio of each photo, be scrubbable (ie let you jump to any section of your archive), handle hundreds-of-thousands of photos, scroll at 60fps, and load near instantly.Īt the time no other photo gallery supported all of this, and to the best of my knowledge they still don’t. My responsibility was the web UI, and more specifically the photo grid. A lot of people contributed to the product - designers, product managers, researchers, and countless engineers (across Android, iOS, Web, and the server) to name just some of the major roles. A few years ago I had the privilege of being an engineer on the Google Photos team and part of the initial launch in 2015.
0 kommentar(er)
