Flutter Heroes 2025

Viktor Lidholt

Viktor is the founder and lead developer of Serverpod, an open-source backend written in Dart for the Flutter community. With a master’s in computer science and over 20 years of industry experience, Viktor has a solid background in software engineering. Before starting Serverpod, he worked at Google’s Flutter team in Silicon Valley. He has held talks and taught guest lectures on programming, app creation, and computer graphics at international conferences and universities such as MIT, Carnegie Mellon, and UC Berkeley.


Your company

Serverpod

Your job title

CEO


Sessions

03-12
12:15
45min
Building a multiplayer drawing game with Dart and Serverpod on the backend
Viktor Lidholt

In this comprehensive session, we will build and deploy a complete multiplayer drawing game. We will explore the synergy of Dart and Serverpod in backend development. Beginning by setting up a Dart project with Serverpod, highlighting the benefits of working with Dart throughout the entire stack. Participants will learn to structure their codebase, write scalable and maintainable code, and leverage Serverpod for backend operations.

A key focus will be on real-time communication. We'll demonstrate how to work with streams to push data from the server to a Flutter app.

The session concludes with deployment strategies, covering the transition from development to cloud environments. We'll discuss containerization with Docker and strategies for deploying to GCP and Serverpod Cloud.

This session is ideal for Flutter developers curious about working with Dart on the backend and backend developers who want to get into Dart.

Main Stage
03-12
17:20
40min
Roundtable
Sasha Denisov, Viktor Lidholt, Marco Facco, Vadym Pinchuk
  1. What exciting developments and features can we expect in Flutter over the next year?

  2. Reflecting on Flutter’s journey, what have been the most game-changing moments and milestones?

  3. Have there been any ambitious ideas or experimental features that didn’t make it to production? What lessons were learned from them?

  4. In what scenarios might companies or developers consider technologies other than Flutter, and how do you see Flutter adapting or responding to such scenarios?

  5. Could you describe any scenarios or use cases where Flutter might not be the optimal choice, and what would you suggest developers consider in those cases?

  6. What advice would you give developers or teams who are just starting their journey with Flutter today?

Main Stage