Oleksandr Leushchenko: When your backend isn't ready

As a mobile app developer, it's not uncommon to rely on backend services to power your app's functionality. But what can you do when the backend isn't ready? Maybe the team is working on a new feature, or perhaps there's a delay due to unforeseen circumstances. In these situations, it's tempting to hardcode data to keep mobile development moving forward. But this approach can lead to myriad of problems, including extensive refactoring and potential issues with data consistency.

Fortunately, there are better ways to handle backend delivery delays, like creating a stub server, deploying a fake server within the app, mocking server, and even mocking a mocked server. As a seasoned mobile engineer, I tried all of that. In this session, I'll share my experience and provide practical examples of how to mitigate backend team delays on a new project.

About the speaker
Oleksandr is a GDE in Flutter and Dart, an experienced public speaker, lecturer, AR enthusiast, OSS contributor, mentor, and mobile developer. He is deeply committed to software engineering best practices, a test-first approach, and automation, which he applies to build digital products for dozens of clients throughout his career.