claimsforce

claimsforce

8 Followers
We create great claim experiences driven by technology

Decisions 2

Kevin Lücke

CTO at claimsforce GmbH

For us it was a long discussion if we should use Flutter in the beginning of 2019. It was still a young framework and only a few team members had hands on experience with it. Our company vision was mobile first but it wasn't sure if the market will follow. What if we have to support more than iOS and Android? It was a bet on the capability of the amazing Flutter team to deliver on their promise to bring Flutter also for Web, Desktop etc. Finally the eco system and provided packages haven't been wide spread.

Now one year later we know it was the right decision and bet. Learning Flutter and Dart was lightning fast for our dev team. Prototyping ideas as fast as possible was no problem at all anymore. We also create open source packages to support the SDKs we needed. And we adapted a high standard of coding by following SOA/DDD. We also created fully automated build pipelines to deliver as fast as possible. No doubt it was the right decision and we also started to use Flutter for web... more to come.

3 963

Kevin Lücke

CTO at claimsforce GmbH

We decided to make use of Segment to avoid adding all kinds of analytics and data collection tools into our apps. Segment helps us to deliver all events to the destinations where we want them to be and it also allows it without the need to get developer support.

To make Segment work with our Flutter apps we also created an open source package to so: https://pub.dev/packages/flutter_segment

2 658