Glad you like it Moyin :)

It really depends on what are you trying to do. If you have a CRUD endpoint, then you can just use shelf_router to mount multiple handlers to this serverless function. If you don't want that, you have to create a new function.

Hi Taha, thanks for sharing your opinion. Macros will never fully replace build_runner because they generate Dart code only, so in the case of Pidgeon or any use case where your output is not a Dart file, macros will not be useful. Also, they are still experimental, but judging only by the preview macro JsonCodable, the way augment class works, also means that they will not work for generating standalone Dart files. Will it replace .g.dart and .extension.dart? Yes. But that's about the extent of it.

Hi Ini, I think Dart has a bright future, but we need more adoption, especially in the backend ecosystem. Google not supporting his own language officially is a shame, but they also have GO, which is widely successful in backend systems. I think Viktor and team at Serverpod are at the forefront of this and I'm looking forward to seeing how the future plays out. For now, Dart without Flutter is a niche tool.

For those interested, I posted this on Reddit and people pointed out some cons of using Flutter for a TV app: https://www.reddit.com/r/FlutterDev/comments/1fi0p0e/flutter_vs_native_why_flutter_wins_for_tv_app/

Glad you like it James!

Thank you Ivan! To answer your questions: Yes, Lottie caches your animations into RAM I never measured the difference, but Lottie is designed for a different use case. The main use case would be complex animations that don't require interactive behaviour. It also requires an Animation designer to design the animation in Adobe After Effects and export it via BodyMovin plugin. Depends on the size and number of animations, but generally not really I prefer to have them locally because it loads faster and you can also control the loading manually like in this StackoverFlow answer .

Thank you Tinz Twins , glad you liked it!