Learning Flutter

-

 I've been learning Flutter in order to help my team out with a new project we are taking on. At first I was skeptical, since cross-platform frameworks usually end up sacrificing something to run on so many different platforms. However, I was really impressed with Flutter, especially when I saw our teams app running in the web, on Windows and on an Android phone, and it looked good on every device!

I started out with the Flutter Development Bootcamp by Dr. Angela Yu on Udemy, where I quickly learned the basics of getting an app set up, changing the app logo, and the core structure of a Flutter application. I wasn't sure about the everything-is-a-widget structure at first, but it ended up making so much sense! I always felt like building something that looks amazing was within reach, and the auto-format always made my code look great. It reminded me of components in React, although I think I prefer widgets.

I ended up building several simple applications while following with the tutorial, before I had to get focused on the actual application my team and I were to be building. Most notably I built a stylish BMI Calculator and a simple Weather app using Android's location services.

What I liked about Flutter:

  • Widgets are easy to use
  • You can peek at the Flutter code and existing Material widgets
  • It's quick to get an MVP up and running
  • There are loads of Dart packages available to use

What I didn't like:

  • Dart is a good language, I felt it similar to TypeScript (I've heard it compared to Swift and Kotlin, but I haven't worked in those languages) but it isn't really used for anything other than Flutter, so it's hard to justify a framework that uses a specific language that you won't use on anything else.
  • Flutter for the web is a bit tricky. It went much better than I expected and actually most of my development has been on a web app, but it's not perfect. Ultimately we want a cross-platform app, so Flutter makes sense, but if you are focused on a web app then I would stick to a web focused framework.

Comments

  1. Tanika Co ValdaSeptember 3, 2026 at 11:32 AM

    The article provides a practical and honest introduction to learning Flutter, especially the author's experience with building applications across web, Windows, and Android. I liked the comparison between Flutter widgets and React components, along with the discussion of rapid MVP development, Material widgets, Dart packages, and the advantages and limitations of using Flutter for cross-platform projects.

    The hands-on examples, including the BMI Calculator and Weather app, make the learning journey particularly relatable for developers evaluating mobile technologies. Readers interested in component-based application development can also explore a React Native Course in Chennai to understand another approach to cross-platform mobile development.

    ReplyDelete
  2. Tanika Co ValdaSeptember 3, 2026 at 11:32 AM

    The discussion about Dart is also useful because it highlights an important consideration when selecting a framework: the long-term value of the underlying programming language. The author's observation that Flutter for web applications can be useful but may not be ideal for purely web-focused projects gives readers a balanced perspective when comparing development approaches.

    It is interesting how the article connects Flutter's widget-based architecture with concepts familiar to frontend developers. Developers who already work with component-driven interfaces may find a ReactJS Course in Chennai helpful for exploring another component-based frontend ecosystem, while practical ReactJS Projects can provide opportunities to apply similar ideas in application development.

    ReplyDelete

Post a Comment

Popular posts from this blog

Catching Unhandled Errors in .NET/C++

-
Most developers are familiar with the pain that comes from an application crashing in production, and not offering any helpful information why it crashed. I recently was tasked with trying to catch some mystery errors, and I learned a lot about how .NET has some built in tools to catch errors in C++. The SetUnhandledExceptionFilter function supersedes the top-level exception handler in a thread, so if you hit an error the function will catch and allow you to do something before everything goes up in flames. This is a great time to do things like creating logs that will give some insight about what went wrong. It'll allow you to get a better idea of why a program crashes in production. Keep in mind, this only works outside of the debugger, so even in Visual Studio you'll need to run without debugging to test this. This code snippet is probably the simplest proof of concept for this tool that I could come up with. Essentially we are going to set the function that will handle our...
Read more

FastAPI for a Simple Game

-
Image
      Since I've been having fun with FastAPI, I decided to build an API for a simple game I learned about while studying my textbook for my Advanced Algorithms course. The game is described as two players attempting to move their pieces from one side of the grid to the opposite side. One player moves from the top to the bottom, the other from the left to the right. A piece can move forward one space into an empty space, or it can hop over one empty piece. Once a player's pieces have moved all the way over to the opposite end of the board, that player wins. The author of my textbook said this game was played on a table in a diner using sugar packets, so I decided to call my game 'Packet Swap'.     Anyway, since I wanted to use FastAPI, the logic is in Python. I found what I thought was a pretty good solution by describing the board as a dictionary of tuple keys and strings describing the object in that location. Using tuples as the keys let me do some...
Read more

Using WebRTC to build a videophone in React and TypeScript

-
 Recently I had the opportunity to spend more time learning React, as well as Redux and a bit about WebRTC. I was prototyping a website that allows you to make video calls to other users, and I thought it was really cool how out-of-the-box WebRTC is. I also used TypeScript, even though I had some trouble in the past with React-TypeScript applications, and it went pretty well. There was some finicky things and it required me to learn the types of objects I had never used before, but overall I think it went pretty well.   The server is built with express, and uses socket.io to emit the web-rtc requests. There is no authentication or authorization, I was mainly focused on showing that I could make a video call.It uses Redux to handle state management, which was a bit tricky in TypeScript and felt like I was writing a lot of repeat code, but it got the job done better than it would have without it. Ultimately this project ended up being put on the backburner as my team turned...
Read more