Thanks for noticing Ian 🙂. Getting a 4K camera and 4K monitor has helped out a lot as far as how clear the screen recording is, an interesting side effect is that it shows you more of the wrinkles and pores on my face in the intros... so there are good and bad things about 4K 😁.
Hm... By the name of the video I thought we will do something like animated icons. For example if you have a home icon for the main screen, then the door of the home image will be opened and closed, when you switch to homescreen and back and interact with home button in the bottom navbar. But make icons selected and enabled/unselected - you can just do it in Figma and then just show it to developers, and they will recreate it quickly :) But was usefull anyway! Thank you :) And yes, quality of the video is just awesome, thanks for investing in it!
Hi Dmitriy, if you look at the examples in the intro, apps that used to animate the tab bar icons in the way you described have now all moved to icons that simply animate between an outlined (Enabled) to filled (Selected) state. This is probably due to the idea that you shouldn't introduce animation unless it's going to add a required level of cognative understanding and value to the element it's been used on. Where you "would" animate onboarding screen illustrations but "wouldn't" animate tab bar icons. The thing I love about Lottie Files is that you author once and deploy anywhere. 1 asset can be used in the web and in iOS and Android native apps without a developer having to do the work themselves (Aside from getting it to play). You also get the situation where you would have to provide, for every icon, 2 SVGs for iOS Android and 2 PDFs for iOS to a developer who would then animate between their states. That's 20 files instead of 5 and you may also get the Android developer creating them in AVD (Android Vector Drawable) which would then have an outcome that is unexpected. With that said, I'm doing an animated bell icon next that does swing and fill when there is a new notification so look out for that soon, and again, thanks for watching! 🙂
Hi Julia. That's odd. Bodymovin should only be exporting a json file that is completely vector. For more complex animated affects it'll export pngs, but for this tutorial they're not required.
@@ChristopherDeane thanks for the response! It took me a lil digging to find out why it wasn’t exporting properly… and it was only because when exporting I wasn’t selecting “current” but the general project instead
