Android developer in an agency team
At Futured, I worked as an Android developer in teams delivering mobile apps for different clients. Sometimes I handled the Android part as one member of a broader team, and on some apps I was practically responsible for the Android development on my own.
I cooperated with PMs, iOS developers, designers, testers and other team members. On some projects, I also worked directly inside teams of other companies as an Android developer.
Coordination happened in Jira. Depending on the project, we usually had regular meetings twice a week, and during more intensive phases every day.
I also did code review and prepared Android talks on topics I studied and presented to the team.
Client apps ARmage, Decathlon, Bit.plus, hello82, CityMove and PeopleCar
Projects from this period include ARmage, Decathlon, Bit.plus, hello82, CityMove and PeopleCar. These were different client projects where the Android app worked as part of a broader product, service or internal operational process.
I worked on Android functionality, screens, application states, service integrations and preparation of changes for testing or release. In practice, that meant combining client product requirements with technical implementation that could remain maintainable across further iterations.
The Android team environment helped me a lot. Colleagues reviewed my code, I could discuss different solutions, learn from others and follow the context of what people across the company were solving on different projects. I value this experience highly.
Kotlin, Jetpack Compose, Firebase and the Google Play ecosystem
The technical stack mainly included Android SDK, Kotlin, Jetpack libraries, Jetpack Compose, Clean Architecture, Firebase, Google Cloud and Google Play Console.
The work also included specific technical areas such as OpenGL, AR augmented reality and hardware integration, including QR scanners and printers.
This experience complements my own Android products and custom internal tools. It is especially useful for clients who need an Android app to become a long-term part of a product, SaaS service, automation or internal system rather than a one-off prototype.
