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...

Canyon Precede:ON 7

I bought or technically leased a Canyon Precede:ON 7 (2022) electric bike last fall. This post is about my experiences with it after riding for about 2000 km this winter. The season was a bit colder than usual, and we had more snow than in years, so I properly put the bike through its paces. I've been cycling for almost 20 years. I've never owned a car nor used public transport regularly. I pedal all distances below 30km in all seasons. Besides commuting, I've mountain biked and raced BMX, and I still actively ride my road bike during the spring and summer months. I've owned a handful of bikes and kept them until their frames failed. Buying new bikes or gear has not been a major part of my hobby, and frankly, I'm quite sceptical about the benefits of updating bikes or gear frequently. I've never owned an E-bike before, but I've rented one a couple of times. The bike arrived in a hilariously large box. I suppose there's no need to worry about damage durin...

Emit structured Postgres data change events with wal2json

A common thing I see in an enterprise system is that when an end-user does some action, say add a user, the underlying web of subsystems adds the user to multiple databases in separate transactions. Each of these transactions may happen in varying order and, even worse, can fail, leaving the system in an inconsistent state. A better way could be to write the user data to some main database and then other subsystems like search indexes, pull/push the data to other interested parties, thus eliminating the need for multiple end-user originating boundary transactions. That's the theory part; how about a technical solution. The idea of this post came from the koodia pinnan alla podcast about event-driven systems and CDC . One of the discussion topics in the show is emitting events from Postgres transaction logs.  I built an utterly simple change emitter and reader using Postgres with the wal2json transaction decoding plugin and a custom go event parser. I'll stick to the boring ...