5 ms·
Author of the iOS side of things here. Feel Free to ask any questions!
by buba447 10y ago
Author of the iOS side of things here. Feel Free to ask any questions!
- hsavit1 10y agoWhich screens in the app are currently are using this?
- hsavit1 10y agoahh I see - I should have looked at the demo gifs!
- film42 10y agoOff topic, but why is the iOS app so big? It's currently 130MB, which is almost 3x larger than the Android app and 10x larger than what I'd expect. Are you guys planning on slimming the app down? Is that 130MB mostly libraries you depend on, or is it mostly fonts, images and other assets? Thanks!
- chris_7 10y agoYou can download the IPA itself and check (they're just zips). Spoiler alert is that the binary (unzipped) is 130mb, but I think this contains multiple architectures.
- buba447 10y agoActually this is perfectly ON-TOPIC :) Some of this come from a mixture of architectures, and the fact we are using Swift+Objc, or just large asset files. Its something we are actively working on fixing. One of the things we did to make it better was build Lottie! Now we can replace PNG sequences and Gifs that can be several megabytes with simple JSON animation files which measure in the low kilobytes. One such example is the diamond animation found on our listing pages. To include this in the project before Lottie we had to package a PNG sequence for each screen resolution(@1x @2x @3x) with alpha these sequences would add around 4-5 megabytes to our app for a single, small, animation. With Lottie we package a single JSON file which measures around 2 kilobytes!
- giarc 10y agoWill this be available for swift?
- hesdeadjim 10y agoFragile and tedious animation authoring is/has been a huge problem on these platforms, you are awesome, thank you.
- 72mena 10y agoMy questions may be off-topic (maybe more fit for an AMA with the design/engineering Airbnb team). First of all, thank you for making this an open-source project. I've noticed Airbnb has been very open with the design community about the internal processes and tools, whereas most companies keep their employees under NDAs. So my 2 questions are: 1. Did your team have to advocate for budget to create these tools, to write blog posts and to share them for free, or did Airbnb already had a plan to support this kind of research? How does this "make sense" for the typical budget-oriented PMs? 2. Did your team approach Adobe to see if they were already working on a tool like this? How does the initial planning go for these kind of projects? Lottie looks super interesting, but the first questions that pop up in my mind are all about the planning and research behind such amazing (side?)projects and the people behind them. Thanks!
- buba447 10y agoGreat questions! 1. Lottie started as a ios hackathon project with our motion designer and me. The idea was to just try and get something out of after effect and simply moving on screen. We ended up getting quite a bit further and wanted to keep working on it. For a while we were working on it in our spare time. Airbnb is a great place for open source. Open sourcing code is encouraged by the company. So we made a roadmap of what we wantsd to accomplish, a list of benefits and gains, along with a wish list of future possibilities for lottie and took it to our managers. Basically we pitched it. We also looped in a few product teams and found a handful of small places to use lottie. We also brought on an Abdroid engineer. After this we got approval to move forward with lottie in a 30/70 type fashion. Over all we spent nearly a year, from hackathin to release, on Lottie. We checked out what others were working on and reached out to bodymovin and squall. I cant remember if we reached out to adobe.
- therealsalih 10y agoI helped out on design/animation side of things for Lottie. Just to add a little more clarification. When we first saw bodymovin we started working on Lottie very slowly. THEN Squall came out, and I basically begged Marcus Eckert to invite me to the private beta. He graciously did and I showed off Squall to all the engineers, we were very excited about it. But after vetting it and having lots of conversations about putting Squall in our app, we ended up continuing to make our own version so we could have more control in the end. After all, we had made so much progress already, we could see the light at the end of the tunnel and knew we only had a matter of weeks to get something usable. We still do use Squall for its dope After Effects preview app in our design work flow though.