Challenges and Lessons from Flutter to Native – The Journey from a 1.6 to 4.0 Rating

Our team undertook a bold project to convert an app developed with Flutter into a native application. In the end, we were able to complete the project and we released the new app as a native application. However, after the release, we faced a sharp decline in the app’s rating, dropping from 4.2 to 1.6. Frequent crashes, sluggish performance, and a decline in overall quality led to harsh user feedback. Why did the quality suffer so drastically? There were several contributing factors: One issue was the way we approached the conversion from Flutter to native. In porting to each platform, we overlooked critical considerations, which made the implementation overly complex. This complexity bred bugs, increased workload, and degraded quality. Many teams in a similar situation might follow a similar path. Another issue was team building. Even though individuals had the necessary skills, collaboration as a team was lacking, which impacted the project’s overall quality. In this project, app engineers, designers, and backend developers each worked in silos without sufficient coordination. After the release, we focused on improving the team. We reviewed various processes, strengthened collaboration, and improved the code. As a result, we succeeded in raising the app’s rating back up to 4.0. We will share these processes and lessons. In this session, we will first discuss why it was necessary to convert from Flutter to native (this transition is generally quite rare!). Then, we will introduce the development antipatterns that caused the rating to drop to 1.6 and explain concretely how we recovered to 4.0. We will pay particular attention to technical improvements and the importance of team building. This session will be valuable not only for app developers but also for project managers and team leaders. Through our experience, we hope you will gain insights for improving quality in app team development. (Translated by the DroidKaigi Committee)

  • Ryo Kitamura RIZAP TECHNOLOGIES,Inc.

  • kentaro fujii RIZAP TECHNOLOGIES,Inc.


Summary

  • Dates 2025.09.12 / 11:20 ~ 12:00 (40min)
  • Place Meerkat
  • Language Japanese (English interpretation available)

Intended audience

Software engineers who value learning from failure: Those who wish to leverage lessons from past projects to improve future ones. Project managers: Individuals responsible for managing development projects who are interested in optimizing team collaboration and project progress. Team leaders/management: Leaders or managers seeking to enhance team building and strengthen teamwork.

Android is a trademark of Google LLC. The Android robot is reproduced or modified from work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License. Android, Google Play and the Google Play logo are trademarks of Google LLC.

© 2014- DroidKaigi Committee