Maestro: E2E tests for Flutter that go beyond your app
Most E2E testing tools stop at the edges of your app. Maestro doesn't. Here's what it is, how it works, and how I use it in OpoSAS to validate real flows on device.
Most E2E testing tools stop at the edges of your app. Maestro doesn't. Here's what it is, how it works, and how I use it in OpoSAS to validate real flows on device.

OpoSAS is an app for preparing Spanish civil service exams: practice tests, per-topic statistics, an AI assistant, and Premium subscriptions. Here's how it's built.
My blog had been on WordPress for years and it worked. But without version control, with a sidebar that fragmented focus, and no reading time on post cards, the time had come to rebuild it from scratch. Here's what happened when I used Claude Code with the VGV Wingspan plugin to plan and build it.

As I mentioned in the post about SOLID principles, we're starting this series with the Single Responsibility Principle — for me, one of the most important principles in software development.

The SOLID principles offer a guide to writing Flutter code that's easier to maintain, extend, and understand. They help you build more robust and scalable applications while reducing bugs and improving collaboration.

After a long time — too long — I'm back to writing. This time we're switching things up and diving into Flutter for cross-platform development.

After implementing FirebaseDB for Android, we wrap up this series with the iOS database implementation.