IISC - Engineering

Regarding Flutter and the Dio package… I’ve been working extensively with Flutter because of its ability to build cross‑platform apps with a single codebase. One thing I appreciate is that Flutter compiles down to native ARM code using Dart’s AOT compilation, so performance is close to native and UI rendering is consistent across iOS, Android, Web, and even desktop platforms.

For API communication, I rely heavily on the Dio package. It’s more advanced than Dart’s built‑in http package because it supports interceptors, global configuration, cancellation tokens, and even automatic request retries. For example, I can inject authentication tokens into every request or centrally handle errors like expired sessions — which is a big time‑saver in production projects. On Android and iOS, Dio integrates smoothly because it uses the underlying platform’s HTTP client under the hood, so networking is reliable and consistent.

On why Flutter over Java/Kotlin… Java and Kotlin are great for Android, but they are single‑platform unless paired with separate iOS code. That means maintaining two separate codebases. Flutter gives me the flexibility to target Android, iOS, and Web without compromising UI fidelity. Also, Flutter’s widget tree and reactive rendering make it faster to iterate and prototype — I can hot‑reload UI changes instantly. In hackathon scenarios, that speed is a game‑changer.

Regarding Supabase in my project… I’ve integrated Supabase as my backend‑as‑a‑service. It gives me PostgreSQL with built‑in authentication, storage, and real‑time subscriptions. The real‑time capability is critical — for example, when I update a user’s location in my project, all connected clients automatically receive the updated data without manual polling. Supabase also plays well with Flutter through its Dart SDK, so I can query, insert, or listen to database changes.