Devmil

Desktop framework comparison

2026-06-30T18:24:57.000Z

Desktop framework comparison

Background

As mentioned in the previous post, I have been working on a process explorer for macOS (Yggdrasil).
I wanted to know how Swift + Rust compares to other frameworks, especially cross platform frameworks, so I decided to build variants of the process explorer in Flutter + Rust and in Kotlin Multiplatform (KMP) + Rust.

To stay in the nordic naming scheme, I decided to give them all nordic names around the Yggdrasil tree which leads us to:

Framework	Name	Status
Swift + Rust	Yggdrasil	Released
Flutter + Rust	Mimameidr	Released (Beta)
Kotlin Multiplatform + Rust	Glasir	In progress

They all share the same Rust library to actually access the process information but differ slightly in the UI and features.
Yggdrasil has the most advanced feature set as it includes a dedicated helper to access more information of system processes and also provides a document preview for exported snapshots. This was just me trying to do as many macOS specific things as possible 🤣.
Mimameidr is a close second. It lacks the helper and the document preview but other than that it is very similar in terms of feature set. It even has some more advanced ways of showing the graphs (you can switch between tree and process only).
Glasir is in the middle of development and I’m not sure if I will put as much work and love into that one as I did into the other two. More on that later.

New applications

2026-06-05T08:02:22.000Z

New applications

In the last few months, I have been working on a bunch of new applications.
Feeling the itch to use all the AI credits I had available and to squeeze out the budget before it reset, I spent almost all of my spare time in April and May working on new projects or project ideas that had been lingering in my head for a while.

Now, in June, I decided to take a step back and slow things down for a bit after my wife complained that I was in my office non-stop. First home office, a short family time during dinner, putting our youngest kid to bed, and then back into the office to work on projects until late at night.

Anyway, that phase was very productive. Now I have one game in the stores, one game stuck at ~70%, another promising game at 80%, and a new process explorer.

I used these projects to experiment with different AI providers, compare their outputs, and analyze the strengths and weaknesses of each to get a better understanding of the current state of AI and how to best use it in different situations (also at work).

One goal was to provide the infrastructure for the applications, define guardrails and basic rules for the AI, and then try to let the AI do as much of the work as possible. I still reviewed the code at a high level (architectural violations and such) and did the commits / PRs manually.

This worked quite well. I took the infrastructure bits from Mirroly (custom DI solution, logging approach, architecture, and abstraction levels), and the first task for the AI was to copy that code and adapt it to the new project.
I think the result was pretty good and helped a lot to get the project up and running quickly.

I feel like this approach also made it really easy for me to detect when the AI was taking a suspicious turn, as just looking at the code areas touched was already a super strong signal. I could then review the code and give feedback to steer it back on track. Basically, I treated the AI as a junior developer and tried to provide guardrails through the code architecture and basic design rules.

But now let me briefly talk about the released projects:

VØID Arc

Why most applications should be cross-platform

2026-02-25T22:06:22.000Z

Why most applications should be cross-platform

I know this is a hot take, and not everyone will agree. Some of you may even “strongly disagree” 😅.

Still, I want to make the case that most applications should be cross-platform - and that users should care about this too.

I’m biased and I admit it

First, I should be honest: I’m biased.

In two major ways:

I’m a Flutter developer. Of course I think that Flutter (or cross-platform development in general) is the right way to go for most applications.
I tend to switch platforms regularly. Android and iOS, macOS and Linux mostly and I hate it when I cannot use an application that I like on my target platform.

So yes, I have strong feelings from both a developer and user perspective.

Monitor Supercharge

2026-02-20T21:47:14.000Z

Monitor Supercharge

You know, I’m a hardware geek and perfectionist. This is a very bad combination.
This already led me into buying plenty of Android phones because there was always something that annoyed me and I knew there was something out there that would do a better job in this particular aspect.

I think I have it under control much better now than in the past but it still hits me and my monitor story is a proof of this 😏.

What happened so far

As described here: Monitor progression I ended up using an Apple Studio Display and was quite happy with it.

Then came my switch back to Android and things weren’t as gold as inside the cage any more so I switched to a Samsung Viewfinity 5k monitor (see Testing old new waters with Linux).

This was also working quite nicely until I tried some gaming on my ThinkPad. The poor Intel IRIS graphics card was hopelessly overwhelmed by the 5k display and one could feel that it was not meant to drive that amount of pixels.

At work we have plenty of 4k displays (most of them from LG) and running macOS on them works quite well. My eyes are bad enough to not distinguish 5k from 4k to be honest 🙈.
BetterDisplay did the rest to enable HiDPI scaling on those monitors so everything was fine.

So I decided to go with one of the lower end LG 4k displays (LG Ultrafine 27US550 to be exact).

This worked OK in my setup and I was a happy man… at least for some time.
Looking at the MacBook Pro screen next to the LG didn’t do the LG monitor a favour…

The return of the Mac

2025-12-17T20:41:00.000Z

The Return of the Mac

Maybe you remember my last post about my journey from a MacBook to a ThinkPad running Fedora …well, it’s over 😀

I really wanted this to work. I have put a crazy amount of effort into configuring my new beloved system exactly the way I wanted it.
I was proud to have this thing that I own completely. New OS distro to try out? No problem: swap out the SSD and run it. Don’t like it? Just install the old SSD again.
Also all the features that KDE comes with are simply crazy. If you imagine that this is being done by hundreds of people who just do that for the fun of it, or because they see some purpose in doing that. Crazy.
All the things that “just work”. I never expected that given my Linux experience from a decade ago.

What Worked

Most of the Things I Do on a Daily Basis Actually Work. at least, Kind Of:

Browsing the web ✔
Building Flutter apps ✔
- Even for iOS (kind of - performance is really bad) ✔
bash, Warp, Bitwarden, Affine, Seafile, Thunderbird, Vivaldi, VS Code, Antigravity, Android Studio - all work ✔
Having Gemini in a Chrome App ✔
Sending files with LocalSend ✔
native Wireguard integration in KDE ✔
having stats like network activity, CPU activity, … in the status bar ✔

Some Things Did Not Work but Were Solvable

Having a Resilio Sync status bar symbol (vibe coded one) ✔
Native GeForce Now app -> Chrome App (more on that later) ✔
A good Git GUI (used Fork on a Mac, which is - hands down - the best Git GUI) -> switched to GitKraken. Not really fast and a bit weird, but does its job ✔
Screenshot tool was really not that good. I use CleanShotX on my Mac, and there is nothing that even remotely comes close. I was about to vibe code my own (✔)

What Did Not Work

MoneyMoney. I tried several Linux alternatives. But that’s just a pile of garbage, to be honest. There was that one application that kinda worked but it looked like a Java application from 2000 (maybe because it was 🤷‍♂️😂)
Wiso Steuer. The tax software I use. There is no way that I would use a web based tax declaration service. I would rather install Windows into a virtual machine, and do my tax declaration in there.

An interesting ThinkPad twist

2025-06-19T13:52:55.000Z

An interesting ThinkPad twist

My Lenovo ThinkPad T14s story got an interesting twist that I never experienced before that led to me owning a Lenovo ThinkPad T14 now.

The original plan

I decided to setup a Windows partition on my ThinkPad in order to make use of my eGPU and play some games. Mainly Cyberpunk 2077 and Diablo 4.

I tried to run the games on Linux using Steam and Bottles which worked but especially Cyberpunk was a bit unstable.

The Unexpected Discovery

So I installed Windows on a dedicated partition and in the initial setup screen of Windows I was greeted with the Microsoft login dialog that weirdly showed the logo of a small German company and the proposal in the E-Mail field also ended with the domain of that bespoke company.

I’m not too familiar with the different enterprise setup options of Windows but I suspected that this notebook still was part of some enterprise program.

The plot Twist

So I contacted the seller and asked what the problem could be. He replied and said he most probably forgot to remove this device in the company’s management software and told me to do this the next day.

Testing old new waters with Linux

2025-04-23T19:46:10.000Z

Testing old new waters with Linux

I was using a MacBook as main device at home since ~2019 and at work since ~2022.

For me MacBooks are a near perfect combination of robustness, ease of use and flexibility.
With the Apple Silicon transition Apple added performance, no fan noise and battery life to that already long list.

The macOS software ecosystem is full of really nice apps. From home banking (MoneyMoney) over system stats (iStatMenus) to awesome Git clients (Fork). All are perfectly tailored to the very limited set of variation that can happen in Apple land.

Then I decided to go all-in: Apple keyboard, iPhone, Apple Watch, iPad and even an Apple Studio Display and I was happily living the Apple dream 😀 (I left out the Apple Mouse. Sorry but everyone needs to have a line that is not crossed 😉)

Last year a few things happened: I got bored, Apple decided to use some really dubious arguments to get itself out of some EU regulations and promised AI things that were not even remotely finished (as it turned out lately they seem to have been caught off guard on that end) so I decided to go back to Android again.

To be honest: It felt wrong in iOS land for me the whole time. I’m an Android developer at heart and I think this won’t change that easily. It feels right to carry a device around that can contain the apps that I love most developing. Maybe weird but I’m sure there are some people out there that can understand me.

Replacing my iPad with a Samsung Tablet made the Apple Studio Display useless for the “tablet connected to monitor” use-case. Not that I do that very frequently but just knowing that this is not an option drove me nuts so I sold the Studio Display and went with the Samsung Viewfinity S9.

So at that point I was already half way out of the Apple ecosystem.

Since the beginning of this year I frequently ran into capacity issues on my M1 MacBook (512 GB) so I was seeking a replacement with more storage (and RAM, I had 16GB).
I quickly configured a M4 MacBook and immediately discarded that idea seeing the price. I don’t have CPU performance issues, I just wanted to increase memory and storage so I also had a look at used MacBooks that meet my requirements.
At that point I realized that it would cost me around 1600€ to do that upgrade.

Creating my first own iOS app

2025-02-20T20:46:14.000Z

Creating my first own iOS app

As teased in the last blog post I was testing quite a few music streaming services.

The problem

One problem I had, was to share songs that I liked with my kids. Yes, it happens from time to time that I like a song that my kids also like. More often than not, they don’t share my opinion on a particular song, but I keep trying 😅
The family completely refuses to switch to anything but Spotify, so I had to find a way to share songs with them that I found on other services.

The solution

There is that cool web service called Song.link that allows you to turn a music streaming service link into a link to a page that contains links to all the other services that have the same song.
Sadly they don’t have an app and only a guide for how to create a shortcut on iOS to use their APIs.
I found an open source Android app that provides a way to use the Song.link API to create these links. They did not offer a way to share the link to the overview page but was meant to directly turn the link of streaming service A into a link to streaming service B.
My first reaction was to fork this project and add the missing feature (including creating an upstream PR).

But I was not 100% happy with this app, so the expected thing happened that happens if you leave a software developer with a problem alone and give him a free version of GitHub Copilot: I started to write my own Flutter app.
This provided the perfect opportunity to create a quite small Flutter app from scratch putting GitHub Copilot to the test and to try out some new Flutter packages.

And back to Google Pixel

2025-02-07T17:08:58.000Z

And back to Google Pixel

After a few months with my Samsung Galaxy S24 Ultra I found a good offer and jumped to the Pixel 9 Pro.
I hope that this “oh this other phone looks nice, too” spiral that affected me a few years ago is not coming back, but I have a few good reasons for this switch 😅
Let me explain how I excused this switch to myself:

Size

Phones nowadays are big.
Much bigger than in the past. What is considered a “normal” phone was a “Max” 7 years ago.
Today’s “Max” phones (like the S24 Ultra) are huuuuge. The pockets of my trousers barely cover the whole phone and god forbid if you need to bend forward to close your shoes.
The only reason for me selecting the Ultra was the camera system. Sadly Samsung still only cramps the best camera they have to offer into the “Max” phone.

Big camera, “small” phone

Then - shortly after I bought the S24 Ultra - Google decided to release the Pixel 9 (what a surprise 😄).
This time they decided to give the “normal” Pixel 9 Pro the same camera capabilities as their “Max” variant.
I was jealous but resisted to immediately jump over to the Pixel.

Raving reviews

Then the reviews for the Pixel 9 Pro appeared.
Great camera, great battery life (for its size), OK performance.
The price for the Pixel 9 Pro (more expensive than the S24 Ultra at that time) was the only thing holding me back.

MediaMarkt offer

Then MediaMarkt had an offer: Pixel 9 Pro 256 GB for €949. Additionally, you get access to the Google trade-in program offering additional €150 on top of what they are willing to pay for an old Pixel phone.
So I looked into my drawer and decided that the Pixel 7 has to go 😀
The current value of the S24 Ultra (with some margin), the additional trade-in bonus, the value of the Pixel 7 and the MediaMarkt offer allowed me to switch without loosing money (I even made a slight plus but lost the Pixel 7).

A few updates

2024-10-04T16:02:37.000Z

A few updates

I’m still alive

It’s been a while since my last post.
The reason is really simple: there was nothing happening that I felt was worthy to share through a dedicated blog post, so I decided to not publish.
I’m still alive and still planning to share stuff on this blog.

dart-apitool updates

There were a couple of small updates for dart-apitool that were mainly driven by remarks or issues from its users.
A couple of changes:

Force `flutter` command

It is now possible to force dart-apitool to use the flutter command even if dart would work as well (if the package doesn’t have a Flutter dependency)
The new option to enable this behavior is --force-use-flutter

Default for `--check-sdk-version` changed

We realized that there is no situation in which changing the SDK constraints of a package leads to breaking consumer code.
Pub will make sure that any incompatible packages are excluded from the dependency tree resolution algorithm.
This means that a package that increases its minimum required SDK might not be usable by a consumer still using a lower SDK, but this consumer just continues to use the package that it used before.
Therefore, we changed the default for this option to off. At the same time we made sure that changing the SDK type is breaking regardless of the value for --check-sdk-version.

Add “missing exports” information to the extract command

Monitor progression

2023-12-16T09:12:13.000Z

Monitor progression

Ultra wide monitor

For years was using a 34” UWQHD monitor from LC-Power, LC-M34-UWQHD-100-C. It was a cheap monitor, but it worked, and it was very wide.

While really getting used to that horizontal space I also was not really happy with the overall quality (picture and build) so one day in 2021 I decided that I need to upgrade my monitor.

At that time I had my 13” MacBook Pro and while the resolution of the monitor was OK it was not really ideal for macOS. I had to use the 100% size mode which is a bit too tiny for my taste. But the next natively supported resolution was just way too big.
There were some tools out there that tricked macOS into rendering a too big picture and then scaling it down to the resolution of the monitor, but those tools need to create a separate virtual screen buffer consumed quite a big portion of my RAM, so I stayed with that 100% scaling.
I used a CalDigit docking station to only plug one cable into my MacBook and have all the periphery connected which I really got used to and didn’t want to miss in any new setup.

Then I discovered the Dell lineup of monitors and saw an Ultra Wide monitor exactly the size of the LC-Power (34”, same resolution, DELL U3421WE) but with much better picture and build quality.

The monitor also said that it has a docking station built in meaning I could get rid of that CalDigit as well, so I ordered one to test.

Once it arrived, and I set it up I was really happy with the picture quality and the overall build quality. The main issue was that I had to decide - in the on-screen menu - if I want to have a higher resolution / refresh rate or higher USB-C speed 🙁
The second - much more critical - issue was that the built-in network adapter seemed to not be compatible with our network system (AmplifiHD at that time, but that’s another story) meaning the moment I plugged the network cable into the monitor the whole network stopped working a few minutes after. This has caused quite a few complaints from family members until I found the cause of this issue 😅.

via GIPHY

Given that I was really happy with the picture quality and because there were no real alternatives (higher DPI) I decided to keep it and live with using the CalDigit Docking station for now.

dart_apitool updates

2023-10-22T09:27:01.000Z

dart_apitool updates

Recently dart_apitool got 2 significant updates. Thanks to all the contributors that made that possible.

1. More robust preparation step

dart_apitool makes local copies of the packages it analyzes

When dart_apitool analyzes packages it has to do some preparation steps in order to make sure the analysis run doesn’t have any issues:

it has to remove any analysis_options.yaml because this file can limit the scope of the analyzer.
This is OK if you want to e.g. exclude files from linting but dart_apitool needs to see all of your files to create a complete model of your public API.
it has to remove an example project as it needs to run pub get to get the dependencies prepared and up-to-date for a successful analysis run.
Some packages have examples bundled with them that sometimes reach into packages via relative paths that live outside the package directory. Those paths are valid inside the package’s repository but are not valid outside of it. A dart_package bundles those examples which means they also live inside the downloaded package and might have invalid relative path dependencies.
As dart_apitool is not interested in those examples it can just remove them from the package directory and run pub get to get the dependencies.

To not interfer with a local copy of the package (in the pub cache or on disk) dart_apitool makes a temporary copy of the package before manipulating it.

why this is complex and created an issue

This works really well. In the past there has been a special issue if a package was referenced on disk and contains relative path depdendencies. To solve that issue dart_apitool had a functionality to analyzse those path dependencies to determine the directory structure it needs to copy to the temporary directory making the relative path dependencies still work.

In the meantime dart (or better: pub) has a new feature: pubspec_overrides.yaml.
This is a separate file that can be used to override dependencies in a pubspec.yaml. As dart_apitool only looked into the pubspec.yaml it didn’t see those overrides and therefore didn’t know about the relative path dependencies that might be defined in there.
A potential solution to that would have been to also parse the pubspec_overrides.yaml file and take the dependencies defined in there into account.

Minimalistic Text will be unavaible in the Google Play Store

2023-08-29T14:56:59.000Z

Dart_apitool updates

2023-05-19T17:13:33.000Z

Dart_apitool got an update!

The recent weeks I was working a bit on dart_apitool.
The major topics were:

Missing export detection

The way Dart allows to define the public API of a package can lead to situations in which the consumer of the API is able to receive an instance of a certain Type but can’t refer to that type directly (e.g. to define a variable or a parameter of that Type).

Let’s imagine a very simple dart package:

- lib
    - some_package.dart
    - src 
        - some_interface.dart
        - some_interface_impl.dart
        - used_type.dart

some_package.dart

export 'src/some_interface.dart'
export 'src/some_interface_impl.dart'

some_interface.dart

#import 'used_type.dart'

abstract class SomeInterface {
    UsedType doSomethingAndReturnInstance();
}

Struggles with the Dart type system

2023-03-16T21:32:21.000Z

Struggles with the Dart type system

How it began: dart_apitool bug fix

It all started with a bug fix in dart_apitool.
The bug was that dart_apitool detected a breaking change on any parameter type change. Most of the time this is correct but consider this change:

/// version 1
void someMethod(String someParameter);

/// version 2a
void someMethod(String? someParameter);

/// version 2b
void someMethod(Object someParameter);

Here the type of the parameter gets changed but in a non-breaking way.
Any already existing call to someMethod will work with version 2a and version 2b.
The reason for this is that widening the type makes the old type part of the supported type space for that parameter.
Of course this is only valid for types passed in (which is the case for this bug as it describes method parameters).

So the goal was clear: dart_apitool has to check if the old type is assignable to the new type to decide if that change is a breaking change or not.

dart_apitool goes bmw-tech

2023-03-02T18:41:13.000Z

dart_apitool goes bmw-tech

Today I have some exciting news to share!

Dart_apitool has been transferred to bmw-tech. The repository as well as the package on pub.dev are now under control of the BMW open source organization.

“Why?” You may ask

There are two major reasons for that move:

1. The need arose at BMW

Dart_apitool has been born out of a need in the “My BMW” development organization. The need for a tool that automatically can check correct semantic versioning of packages to avoid creating a mess when modularizing the app.
Puzzled by the realization that no such tool existed I took this as a challenge and made the development of dart_apitool my evening pet project.

2. BMW is the only user that I’m aware of

Besides not getting much traction in the Flutter community dart_apitool is used internally at BMW and already got some contributions from BMW colleagues.

I’m not sure why there is a lack of community traction. I can imagine those reasons:

dart_apitool improvements

2023-02-18T08:51:40.000Z

dart_apitool improvements

There has been some new development in dart_apitool.

I got some feedback from our internal “My BMW” app teams and from the Flutter community so dart_apitool has received some extensions, improvements and fixes the last months:

Warp terminal

2023-02-16T22:10:48.000Z

Warp terminal

The Terminal app is the Software developers best friend. This is the most used tool followed by the IDE (ignoring the Browser of course).
As you can see in the blog posts I did I experiment(-ed, more on that later) with building my own Terminal application so that I can stuff in all the features that I want to have in the terminal I use.

Sometimes you are so used to the status quo that you are not able to imagine that the tool you use so frequently could be so much better. The same thing happened to me with Terminal apps. The core of every terminal application was basically the same. The way you enter commands, the way your input gets mirrored, the way the output of the command gets shown and so on.
There are a few options to tweak things and enrich the capabilities of this experience like oh-my-zsh or Oh My Posh to name a few.

But then came Warp.

Antlion ModMic Wireless

2023-02-06T22:04:36.000Z

Antlion ModMic Wireless

This is just a small post about a small gadget I bought recently: The Antlion ModMic Wireless.

Headset issues

Headsets were always a bit problematic for me. Already “in the office” but even more so in a Home Office or hybrid setting.
This issue might be home-grown, but I really hate wired headsets. The cable is always in the way and regardless of the side the cable is at it always interferes with me operating the computer.
So I needed something wireless.
I already have a couple of Bluetooth headsets, but they are not good for voice communication. They have to switch to “HFS/HFP” mode to use the microphone which totally kills the audio quality. Another issue with them is that the microphone quality is lacking, so this was not a good option.
For some time I used my Gaming headset for Teams meetings at the home office. This worked quite good, although the sound quality is nothing I want to listen to music with.
As the Gaming headset started to break I decided to look for another solution.

Gaming Headsets

The big advantage of that Gaming Headset is that it is wireless using a proprietary 2.4GHz protocol. This means that the headset is not dependent on Bluetooth and the audio quality is good even with activated microphone.
Looking at the current market for Gaming Headsets revealed a couple of good options that could replace my old one but still not being a good option for listening to music.
Gaming headsets - especially the good ones - also tend to show off that they are gaming headsets. Not that this would be a problem, but I don’t want flashing LEDs on my headset in a Teams video call 😁 (I know that this can be turned off for most of them, but you get the point).
There are some Bluetooth headsets out there that get quite good microphone reviews, but they lack in music playback quality.

Some dart_apitool updates

2022-11-19T12:01:38.000Z

Some dart_apitool updates

In the recent months I have been working on some updates for dart_apitool.
The main changes I did were:

Removal of using model files

After thinking more about the use cases for the option to store a public API model to a file in order to use it later to diff against a new version I came to the conclusion that this won’t be used in practice very often.
The amount of maintenance needed to support loading older versions of models and support comparing that with a new model based on the current code base was too high for that feature not being used by anyone.
So I decided to just remove that feature completely.

via GIPHY

Generalization of “classes”

Dart_apitool already supported the analysis of real “classes”. As interfaces in Dart are just abstract classes they were supported automatically.
But there are other concepts in Dart, that are quite similar to classes but not exactly the same. Things like Mixins for example.
So I decided to change the API used in dart_apitool to handle all those entities as “interfaces”.

Required interface support

We had a problem with the sqflite package at work. It published an update to an internal package that broke our build. Using that as perfect feature request and integration test for dart_apitool I analyzed what exactly caused the issue.
Dart_apitool would not have been able to detect that breaking change. The reason for that is that it was not aware of the difference between “required” and “provided” interfaces.

Devmil

Desktop framework comparison

Desktop framework comparison

Background

New applications

New applications

VØID Arc

Why most applications should be cross-platform

Why most applications should be cross-platform

I’m biased and I admit it

Monitor Supercharge

Monitor Supercharge

What happened so far

The return of the Mac

The Return of the Mac

What Worked

Most of the Things I Do on a Daily Basis Actually Work. at least, Kind Of:

Some Things Did Not Work but Were Solvable

What Did Not Work

An interesting ThinkPad twist

An interesting ThinkPad twist

The original plan

The Unexpected Discovery

The plot Twist

Testing old new waters with Linux

Testing old new waters with Linux

Creating my first own iOS app

Creating my first own iOS app

The problem

The solution

And back to Google Pixel

And back to Google Pixel

Size

Big camera, “small” phone

Raving reviews

MediaMarkt offer

A few updates

A few updates

I’m still alive

dart-apitool updates

Force flutter command

Default for --check-sdk-version changed

Add “missing exports” information to the extract command

Monitor progression

Monitor progression

Ultra wide monitor

dart_apitool updates

dart_apitool updates

1. More robust preparation step

dart_apitool makes local copies of the packages it analyzes

why this is complex and created an issue

Minimalistic Text will be unavaible in the Google Play Store

Dart_apitool updates

Dart_apitool got an update!

Missing export detection

Struggles with the Dart type system

Struggles with the Dart type system

How it began: dart_apitool bug fix

dart_apitool goes bmw-tech

dart_apitool goes bmw-tech

“Why?” You may ask

1. The need arose at BMW

2. BMW is the only user that I’m aware of

dart_apitool improvements

dart_apitool improvements

Warp terminal

Warp terminal

Antlion ModMic Wireless

Antlion ModMic Wireless

Headset issues

Gaming Headsets

Some dart_apitool updates

Some dart_apitool updates

Removal of using model files

Generalization of “classes”

Required interface support

Force `flutter` command

Default for `--check-sdk-version` changed