Skip to main content

Flutter summer project

As a summer project, I helped out a team at my local university in a project combining open data with students seeking an apartment to rent, especially when moving to a new city. They designed a mobile app for this task, and I was to implement it.

I decided to try out Flutter this time instead of react-native.

Again, there are several blog posts and even official documentation on how to transform from native or react-native development into using Flutter.  Here are my two cents though

Dart. Google's solution for building UI:s. The syntax is familiar looking. I like the way how it is not limited to any particular form of programming, but the guideline for Flutter enforces a specific declarative style. One of the best parts of Flutter development is the named arguments.

Development environment. One of the better setup experiences. A self-contained diagnostic tool which alerts if something is not set correctly. Updating is a simple git pull and some installation scripts. I had no trouble in running the application in either IOS and Android simulators.

Flutter library. Out of the box, Flutter contains all the necessary UI elements (with Material design) for your simple Todo app. The elements or widgets in Flutter terms are split into stateless and stateful. The stateful ones have a well thought, although a bit verbose, manner of separating the state from the UI logic in a declarative way.

Testing. I only wrote plain old unit tests for the business logic and some UI tests using the flutter_test framework. I would say it is on par with react-native testing. I have yet to see a unit test framework for UI components which would work intuitively, and while Flutter certainly worked ok, I had some problems with gestures.

If I had to choose between Flutter and react-native, I would undoubtedly choose the former, especially if new to mobile development.  Main reasons are, in my opinion better, typed, UI widgets, better development environment (including an excellent vscode plugin) and an overall faster and snappier app as a result.

Comments

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro...

PydanticAI + evals + LiteLLM pipeline

I gave a tech talk at a Python meetup titled "Overengineering an LLM pipeline". It's based on my experiences of building production-grade stuff with LLMs I'm not sure how overengineered it actually turned out. Experimental would be a better term as it is using PydanticAI graphs library, which is in its very early stages as of writing this, although arguably already better than some of the pipeline libraries. Anyway, here is a link to it. It is a CLI poker app where you play one hand against an LLM. The LLM (theoretically) gets better with a self-correcting mechanism based on the evaluation score from another LLM. It uses the annotated past games as an additional context to potentially improve its decision-making. https://github.com/juho-y/archipylago-poker

"You are a friendly breadwinner"

A recent blog post by Pete Koomen about how we still lack truly "AI-native" software got me thinking about the kinds of applications I’d like to see. As the blog post says, AI should handle the boring stuff and leave the interesting parts for me. I listed down a few tasks I've dealt with recently and wrote some system prompts for potential agentic AIs: Check that the GDPR subprocessor list is up to date. Also, ensure we have a signed data processing agreement in place with the necessary vendors. Write a summary of what you did and highlight any oddities or potentially outdated vendors. Review our product’s public-facing API. Ensure the domain objects are named consistently. Here's a link to our documentation describing the domain. Conduct a SOC 2 audit of our system and write a report with your findings. Send the report to Slack. Once you get approval, start implementing the necessary changes. These could include HR-related updates, changes to cloud infras...