Worked on the iFood for Partners app, I've changed to a Senior position after leading the development on the Order Manager module, which was our biggest challenge yet: converting an entire Android app to Flutter so we can publish the Order Manager feature to iOS users after years on demand. Dealing with background tasks that need to work with our database, managing a deeper push notification integration and security/permission issues was the main focus of this, all that while still improving our own defined architecture.

For my second challenge within the app, I was tasked with writing a Flutter client for iFood's server-driven UI framework: Firefly. It involved parsing specific payloads into components to render our handshake flows between restaurant and user, dynamic form management and integrating that into our existing occurrences status for each order.

While working on those challenges, I also helped with interviews, meetings with other teams to solve issues pertaining to our app, built analytics dashboards with Amplitude and Databricks, and helped a bit with backend debugging, all while also managing what I could for our team to keep working fast and efficiently.

Worked as Mobile Software Engineer for the client-side Flutter app, helped the team develop new features such as backend-provided dynamic forms and pages and a transition to implement a new state management flow throughout the existing app.

Wrote the Dub app in Flutter and published on both App Store and Play Store. Had experience writing audio player plugins in Swift/Kotlin, porting a RTMP audio-streamer library to Flutter and also working in a fork of ion's WebRTC client. The app works as an audio-only streaming platform, where you can listen to anyone live while also chatting.

Worked as the main Mobile Developer using Flutter and also as backend engineer for two apps, tap.style and what.pet. Used Cloud Run instances to run Machine Learning models based on each app (recognizing the user's style based on clothing, and animal breed detection based on photos). The backend was entirely made with Firebase, using Cloud Functions for most intensive tasks and Firestore as the database.

A messaging app where each user only has access to one message at a time, which gets overwritten by all subsequent ones through editing, instead of following a message chain. Its main purpose was to learn new technologies, such as a Flutter and a proper setup for a Firebase-only project; it's also published to both app stores.

Every factory problem is reported by the manufacturer, but many people end up not being notified, and that's dangerous! PapaRecall notifies you of each recall and leaves you more relaxed.

My first try on the startup ecosystem, and also my final project of my graduation. My responsibility on this project was design its architecture and REST API, elaborate a Value Proposition Canvas based on market research and also implement its Android client; Both Android applications were entirely made with Kotlin, a MVVM architecture with FastAdapter and Data Binding, Retrofit and RxJava/RxKotlin for networking and the Support Library for its design; Luki also was exhibited at Campus Party 2018, in São Paulo. There's also their iOS' versions in the works, both made with Flutter and during this development, I published an article on Medium on how to implement phone authentication with Firebase that got accepted by the Flutter Community group.

Second part on the series talking about our new UI architecture based on Bloc, also explaining what exactly we had before and what changed

I wrote about our three-part journey on rewriting, refactoring and redesigning our app to get to a place where everyone feels comfortable adding new features while managing the existing ones whether they’re new to the team or not.

Need to setup your API keys without hard-coding? I wrote a quick tutorial on how to use --dart-define to pass values onto your app, either in Flutter, or native Android or iOS if you wanna use a native library