This week in Flutter #86: Getting closer to Flutter Forward
More content has been shared this week for the 17 days of new Flutter content. We are getting closer to the Flutter Forward event, and, after some technical problems at the start of the week, this is the new content:
- (DartPad) Play Pong Built with Flutter & Flame;
- (Codelab) Using FFI in a Flutter plugin;
- (Livestream) The Boring Show - LIVE!;
- (Video) Dart Analyze & Fix - this saved me a couple of months ago after changing the analysis options of a monorepo project;
In addition, a couple of blog posts were also shared, linked down below.
- Michele Volpato
Development in Flutter 🧑💻
How I built and published a Flutter app in 48 hours
by Christos
Read how Flow, a money tracker app, was implemented and published on the Google Play Store in a work week. Which packages and plugins are included? Which state management solution? (hint: it is my favorite one).
Creating inclusive apps with Flutter: Best practices for accessibility
“Flutter provides a number of built-in features and best practices that developers can use to make their apps more accessible, including support for screen readers, automatic text contrast, and the ability to add semantic labels to widgets.”
Learn how to make sure your Flutter app is usable by everybody.
Playful typography with Flutter
by Brian James
Explore creative use of variable fonts and shaders in Flutter using FontVariation and AnimationController.
Material 3 for Flutter
What new features have been added to Flutter regarding Material 3? And what is coming next?
Backend for Flutter developers 🗄
Building a multiplayer quiz game with Flutter and Supabase
by Christos
The Supaquiz project was the winner of the Best Flutter Project in the Launch Week 6 Hackathon Winners. How was the project implemented?
Tools to improve your Flutter experience 🛠️
Screenshots and automated publishing for pub.dev
You can now declare screenshots for a Dart package on pub.dev. And you can easily publish your package by using GitHub Actions. Read more about the implications in case you want to go this route.
Software engineering in general 👨💻
6 Best Practices to Manage Pull Request Creation and Feedback
by Jenna Kiyasu
It can take you some more time when handling pull requests, but a good culture is important for your software engineering team. What I like to do is to provide enough context in the PR description, so that the reviewer does not need to navigate to some far-away Jira issue. What I also like to do is add the same description in the squash commit, so that from the repository you do not need to navigate to GitHub/GitLab/Bitbucket.
That’s it for this week.
If you want to comment on any of this week’s entries, you can do it in the comment section below.
Have a bug-free week,
- Michele Volpato
Leave a comment