はてなブックマーク

If your Flutter app talks to a 3rd party API that requires an API key, where should you store it? According to various sources, for production apps that need maximum security: the API key should be stored on your own secure server (and never on the client)it should never be transmitted back to the client (to prevent man-in-the-middle attacks)the client should only communicate with your server, whi

When building complex apps, choosing the correct app architecture is crucial, as it allows you to structure your code and support your codebase as it grows. Good architecture should help you handle complexity without getting in the way. But it's not easy to get it right: “Not enough” architecture leads to poorly organized code that lacks clear conventions“Too much” of it leads to over-engineering,

Flutter Project Structure: Feature-first or Layer-first? When building large Flutter apps, one of the first things we should decide is how to structure our project. This ensures that the entire team can follow a clear convention and add features in a consistent manner. So in this article we'll explore two common approaches for structuring our project: feature-first and layer-first. We'll learn abo

Riverpod is a reactive caching and data-binding framework that was born as an evolution of the Provider package. According to the official documentation: Riverpod is a complete rewrite of the Provider package to make improvements that would be otherwise impossible. Many people still view it as a "state management" framework. But it is much more than that. In fact, Riverpod 2.0 borrows many valuabl

In this tutorial I give a detailed overview of a production-ready architecture that I've fine-tuned over the last two years. You can use the included starter project as the foundation for your Flutter & Firebase apps. Update August 2021: the starter project was originally written using Provider, and later updated to use Riverpod. This tutorial is now up to date and also covers Riverpod. Motivation