DEV Community: Daniele Bertella

Gatsby or not Gatsby. What's Next 😍?

Daniele Bertella — Fri, 20 Nov 2020 20:16:21 +0000

Disclaimer: I'm a Big Gatsby fan and I built multiple website with it. I love its simplicity especially the rich plugin ecosystem. That is brilliant! I also love theme-ui that is the css-in-js library made by people from Gatsby, I'm using it literally every time I can.

I wanted to start a new project. I knew that this time it would have been slightly bigger than my usual pet projects. I was going to build a full website with a possibility to turn it into an e-commerce lately. (And I did btw cascinarampina.it)

I thought a lot about it, I felt quite confortable in starting it with Gatsby but I also wanted to use this opportunity to try something new. Since Next.js just came out with its beautiful version 10 I decided to give it a go. I have to say, that was 🤯

Before talking about Next.js I have to spend a couple of words about the CMS choice. In the past I tried Netlify Cms, Dato, Sanity and I evaluated a few others... As a "Single Front End" engineer I'm always looking for something easy to configure and possibly free or at a very low cost. All those solutions are brilliant and let you build whatever you want at no cost. But for this project I thought I might have needed something more than the free tier especially with form submissions so I looked elsewhere.

Wordpress! Right! Not long time ago I promised myself I would never touch Wordpress again. And here I was, finding myself 😉 to WP again. I don't regret the choice! With the help of a few plugins Wordpress it's a very valid choice as an headless CMS. Not to mention that I could delegate the data entry to the friends I was going to make the website for. Life is beautiful!

Next.js

I have to say I'm impressed by how simple it turned out to set up to go from 0 to have a website up and running fetching data from my CMS. I don't have experience with previous versions but v 10 it's brilliant. All you need to know about the new release is that there are 3 possible functions you need/can export from your page components. No other configurations. Nothing else. It's a bit weird to have those "random" functions at the end of your component but once you understand them it just clicks!

`getStaticProps` (Static Generation) 🔗

This is the function I used most and it's the function that lets you pass props to your page at build time, that means you are creating a Server Side Generated page (SSG)

`getStaticPaths` (Static Generation) 🔗

This is the function you use to generate pages dynamically. The file name should be something like [slug].tsx and Next will be able to generate pages for every slug the function returns. It works well with getStatiProps.

`getServerSideProps` (Server-side Rendering) 🔗

This is the function that turn your page in a Server Side Render page (SSR)

The functions above are mutually exclusive, you can't have getServerSideProps and getStaticProps functions exported from the same page.

But basically at any given point you are free to decide to have an SSR or SSG page and have a webiste that mixes the two approaches. To be fair my SSR pages are very slow to render, probably due to my CMS 😅 performances, so I opted for having all the pages generated at build time.

Another killer feature is the ability to add NodeJS endpoints directly in the same app. Well done to whoever thought of something like that, if I only think at the possibilities, it's incredible for me. Being able to generated a static site at build time and have node endpoints it's just WOW! For instance you'll be able to call resources protected by CORS and provide them to your ui being on same origin. 💣

All of this with no setup at all! No custom servers nothing more than what is built-in in Next.js

Not everything is 💅

Unfortunately, despite of all the above awesomeness I also found a few things that I didn't enjoy and here the comparison with Gatsby kicks in in their favour.

Showing Active Links in the menu bar. There is not a simple prop in next/link component. It's not complicated to build your own and listen to routes changes to adapt the style. But it's some more work to do to accomplish such a simple thing.
To generate an xml sitemap ain't easy. There are a few examples out there, feel free to look at my implementation if you wish or look at this issue to have some ideas, anyway, thinking at the Gatsby way I 😭 a little loosing my nights handling SEO related tasks.
To add Google analytics and send correct data you need some custom implementation, that's not that bad but again in Gatsby, with its official plugin comes (almost) for free.
To generate manifest and app icons I used an empty Gatsby instance, another very useful plugin I can't live without. 🙀 So ok, this isn't something bad about Next, but something I missed here for sure.

Conclusion

I really enjoyed this project and Wordpress + Next.js seems quite a solid choice for my next project(s).

In the meanwhile, though, I made on my personal website danielebertella.com and I decided that there was no point in using Next.js.
To build a static website in a night Gatsby is still the best choice for me.

Right now I can't decide what's better actually. I'm looking forward to what Gatsby team are going to release next, I heard quite nice stuff are coming. We shall see!

And you? What would you choose for your next project? Let me know! I'm super interested in the topic!

Cover image from cascinarampina.it
Thanks Mike for the proof reading 😉

Publishing my Flutter App on Google Play Store

Daniele Bertella — Wed, 10 Jun 2020 13:00:46 +0000

I finally published my first app in the Google Play Store. Hector the little dinosaur is live!

This was a great journey and the Flutter code was the easiest part of the whole process.

Publishing on the Play Store is not straightforward, and I didn't even face the App Store yet. Every time you publish a new release you will need to wait for Google to review and make it available even for an internal test. Normally it takes just a few hours. I was publishing new tests at night and they were visible the morning after. At times, especially at the beginning, it took days.
The issue is the lack of control with no clear indication. You wait for a notification and after that you also wait some more in order to see the changes in the store.

I left all the store listing optimisation to Aurelie since she is the author and illustrator of the book, and accessorily an SEO/ASO expert! 🙀 That's why it looks very good!

Here are a few milestones I'd like to share.

May the 27th: App live for the first time!

This was the first time I've seen the word published close to the app listing. I received a notification saying the app passed the review and it was live but in reality I had to wait a good half a day in order to be able to share a link to install it. It's an internal beta so just a predefined set of friends had access to it. People also needed to follow a particular process in order to install this test version. Here is the documentation about it.

Jun the 4th: Public Beta!

Internal testing is great but not exactly easy to send to friends and family so I decided to move to a public Beta.
The App was working fine and after some feedbacks we decided to change a little the ui. Now images are not cut and they fit into the page leaving black borders around and we also added next and previous button in order to make the navigation more explicit.

Jun the 9th: Pushing the red button 🚨

After a couple of public betas it's time to promote the last one to Production. I don't know how long it will take but it should be available soon.

Jun the 10th: The app is live

Here is the link to the play store where you can finally find the app! https://play.google.com/store/apps/details?id=hector.the.little.dinosaur

That was `definitely` the beginning of a beautiful friendship!

This is how the book finishes and how this series of post about my first app written in Flutter ends.

I don't regret the choice. I found working with Flutter quite interesting and fun. I had a small amount of issues during the development and I was able to find a way out from all of them. It has been a great experience, everything went very well.

I can't say I'm an expert now, I would rather say I'm a junior Flutter developer but I'm a proud publisher! I made different websites in the past but publishing an app has been a completely new experience and I'm really happy to have done it.

Time to Publish my First Flutter App on the Play Store (a Week After)

Daniele Bertella — Thu, 28 May 2020 11:28:21 +0000

This is a follow up from my previous article in which I was thinking I was very close to publish my first app on the store. It turned out that I needed to complete all the forms before being able to publish anything, even an internal test track.

I spent last week waiting for something to happen and at the end I realized that I was missing informations. Now that everything is ready, my app has been finally submitted for review.

Current status, Pending publication 🥶

Pro Tip: make sure all the ticks are green ✅ before to try to roll out a release next time!

The process involve all the store listings, screenshots and feature graphic.

I would say try to speed up the process. So even if you don't have the final version of your graphic you will be able to amend them later. The app I'm submitting will be free so I didn't go through the setup of the merchant account. Maybe I'll keep this option for the next time 😅.

Also something to keep in mind. Test the app locally! I was waiting for the it to be available in the store to start to test the release but actually it turned out it was a silly thought. You will need lot of iterations before your app will be ready.

In this case building an apk instead of an appBundle it will make testing way easier.

Just run:

flutter build apk --split-per-abi
flutter install

with your device connected and you will be able to test your released version of the app.

This helped me to understand for example that google fonts aren't embedded by default (my bad I didn't read the documentation at first here a SO on the topic).

Anyway in the meanwhile I was able to add a little animation in the homepage using lottie plugin.

Flutter (😂) of a butterfly with lottie

Super nice right? I spent some time to understand animations in flutter, my issue was that I wanted to pause it for 10 seconds before to start it again. I had some fun, if you are interested I can share more details on the topic, eventually in a different post.

I also played a lot with sounds, now we will have a soundtrack too thanks to Cecilia Fumanelli.

The goal to have my first Flutter app on the store is closer than ever. I'm still not quite sure how the private testing will work, I suppose I will have a link to share with my internal list of predefined people but I guess I will have to wait for the review before.

I will keep you posted!

Hector the little dinosaur written and illustrated by Aurelie Mercier. Cover image is also part of the book.

Time to Publish my First Flutter App on the Store!

Daniele Bertella — Wed, 20 May 2020 19:31:15 +0000

If you didn't read my previous articles, I’m building a Flutter app for a children's book¹. If you want to check it out: Hector the little dinosaur. The cover image is also part of the book and is not related to Deno at all, I think must have copied from Hector 😂. Last time I did any mobile development before was more than 2 years ago with React Native.

The day to publish the app came 👊

Well at least that's what I thought 😭. Finally, my partner and I finished recording all the pages read by my 4 years old son. These are not perfect but for as first iteration they would suffice, and that was the hardest part of the whole process! So I decided to publish the app for an Internal test track and...

Look at that! I guess I will need to wait for someone to look into my app before I can try a released version from the store.

Anyway I think it's worth sharing the journey.

Icons and Splash screen

Even before you can submit to the store you want to have a nice launcher icon and a splash screen.

For the icon part Flutter got your back, with this plugin it's very easy to generate all the possible icons with the right formats, no need to waste your time.

The splash screen however was a little bit more complex and required some manual processes. For the iOS version you must use XCode for this. All you need to do is modify the LaunchScreen.storyboard file that you find in the iOS folder inside the project.

I didn't get how to scale the picture but it'll be fine. You need to play a little with settings, but it's quite intuitive even if you don't have much experience with it. I didn't want to mess around too much I just added a picture in the middle and that's it.

For Android I had to modify launch_background.xml and I needed to play a little with it to have something ready.

<item>
    <shape android:shape="rectangle">
        <solid android:color="@android:color/white" />
    </shape>
</item>
<item>
    <bitmap
        android:gravity="center"
        android:src="@mipmap/launch_image" />
</item>

The code above is how you can have a centered image with a white background, default colour would have been black otherwise.

This is my folder structure so basically I have icons in all sorts of resolutions (generated by the plugin) and splash screen images in various resolutions randomly scaled by me, since I didn't know exactly which resolution goes to which folder, once again, the images are probably too big but it will be ok until I will dig more into the possible settings.

Build the app for release 💣

Flutter documentation covers this section very well so I won't go into too much details. I just got confused at some point when Goole required me to enroll into app signing by Google Play and following the steps it looked like they just made me sign the app again with Android Studio instead of the command line. I probably accepted some terms and condition in the process but anyway, somehow I managed to have my bundle ready to upload!

Sign up for a developer account 💸

Google charges you "just" $25 to let you publish the app on their store, while Apple charges you £79 for the same thing!

I subscribed and the journey began!
Lost in the Google Play Console! Loads of options and way too many forms to fill, I tried to publish this internal test version but I had to give up since the final button is just disabled and I believe it's because someone need to check the content of my app.

Also, since my app is targeting kids I needed to add a mandatory privacy policy that I generated on a random website 😂 and uploaded on the Hector site

Conclusion 🍕

Nothing is lost, the app is good looking I will need to deal with some bureaucracy but soon I will be able to publish my first ever app on the store! And I'm super excited by this.

Also, I don't want to spoil too much, but my previous articles created a snow ball effect! Someone is building Hector in React Native! Stay tuned but soon we might be able to make a very good comparison!²

Hector the little dinosaur written and illustrated by Aurelie Mercier. Cover image is also part of the book. ↩
As usual thanks to Peter for the english corrections here and there ❤️. ↩

What I Really Like About Flutter so Far

Daniele Bertella — Mon, 18 May 2020 07:44:50 +0000

If you didn't read my previous articles, I’m building a Flutter app for a children's book¹. If you want to check out: Hector the little dinosaur. The cover image is also part of the book and is not related to Deno at all, I think they copied Hector 😂. Last time I did any mobile development before was more than 2 years ago with React Native.

My expertise right now is React and TypeScript and when I started with Flutter I was skeptical at first. The syntax may scare you at, it looks quite similar to Java (so I've been
told) and the way you build the UI feels to me how React did it a year or so ago before the introduction of hooks 🙀.

In this article however I'd like to highlight what I really like about Flutter and Dart.

Everything just works! 🤘

The thing that I like the most, is that it seems that everything just works! It's amazing, I don't have much experience in mobile development but the few times I approached it, it hasn’t been easy. This time, I have to say I'm pleasantly surprised!

A Super Cli 🔥

As I mentioned already in a previous article, tools are quite nice and probably superior than the ones available for JS/TS.

Once everything is set up, you can run flutter run with a device connected (or a simulator open) and the app is up and running. No need to run it with Xcode or Android studio. Basically no need for an IDE at all. You still need to have them installed along with the native SDK but at least while writing code you don't need to open them that often and that's a big 👍for me!

Hot reload is available while running the application in the command line. It felt weird the need to press R in the terminal in order to hot reload the app but I got used to it pretty quickly.

Also pressing P while running gives a very useful overview of all widgets and how they are positioned on the screen.

My current homepage running in the simulator after pressing P in the cli

Debugging is straightforward too.
This is the whole setup needed to run the app in the vscode debugger.

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Flutter",
      "request": "launch",
      "type": "dart"
    }
  ]
}

There are other useful command, such as flutter create to start a new project, flutter doctor to help you with the setup and to check that everything is fine for the development. If you want to know more, here is a complete list of useful commands: https://github.com/flutter/flutter/wiki/The-flutter-tool

VS Code integration 👀

The integration with vscode is amazing. After installing the Flutter plugin you will have: error handling, autocomplete and documentation on definitions available in the editor.

Example of code hovering over RoundedRectangleBorder

I would say that you have the same experience that you expect working with TypeScript and probably a little more! The compiler feels faster and more accurate.

I can’t entirely compare due to the different scale of projects I'm working on, but Flutter (and probably Dart) left me with a very good impression overall.

Native feeling 🤞

I still need to see how the app behave once I publish it but so far even in debug mode it seems like a Native app. I’m interested to see how it looks, but so far I can't complain.

Also I needed to integrate with the native side 😼 for the audio. I wanted to load audio files from assets and I installed this plugin along with some native libraries. I had some issues with cocoapods installation (iOS dependencies) but after fixing that, everything just worked fine.

Also installing new dependencies can be done from CLI manually or adding a line to the equivalent of the package.json, pubspec.yaml, which triggers the installation command flutter pub get for you in vscode.

Wrapping it up 💣

I'm very happy with what I've seen so far and I would recommend to just install Flutter download the repo https://github.com/dbertella/hector-app and try it out. The syntax might be challenging at first coming from React but as soon as you realise that it's actually very similar and you might find out that the DX will be even better.

Don't forget to let me know if you try it and end up liking it!!²

Hector the little dinosaur written and illustrated by Aurelie Mercier. Cover image is also part of the book. ↩
As usual thanks to Peter for the english corrections here and there ❤️. ↩

Add a Navigator to a Flutter App

Daniele Bertella — Thu, 14 May 2020 17:14:26 +0000

Navigators have always been a pain while making a React Native app. With many third party options and not a clear way to go. They probably got better lately, but adding one in my Flutter app has been a breeze.

As always, there's an existing, specific widget to handle that and it's called Navigator.

It took me just a couple of hours to have my home page up and running. One single button with an image coming from the assets that let you navigate to the Story. Very nice!

All you need to do is to create a list of routes, in my case a list of one for now 😂, and make a Map out of them.

class Page {
  final String route;
  final WidgetBuilder builder;

  const Page({this.route, this.builder});
}

final routing = [
  Page(route: '/story', builder: (context) => Story()),
];

final Map<String, WidgetBuilder> routes =
    Map.fromEntries(routing.map((d) => MapEntry(d.route, d.builder)));

The MaterialApp, the root of the application, accepts a Map of routes as parameter:

MaterialApp(
   title: 'Hector the little dinosaur',
   routes: routes,
   home: HomePage(),
);

And basically that's it!

After this setup you'll be able to interact with Navigator API. In this case a FlatButton that invokes Navigator.pushNamed('context', '/story') API with current context and the name of the route I want to load: /story.

Inside the Story class I have a button that perform the pop action: Navigator.pop(context);

I looked at this example from the official documentation in order to get some inspiration but I had some issues with the spread operator with the SDK version I installed so I just simplified it to the bare minimum.

The Story Widget

To control the story flow, I found a very useful Widget called PageController that gives me exactly what I needed: a slide to next / prev page in a very efficient way. So I didn't have to reinvent the wheel.

Important thing to notice is that since this Widget doesn't add new views on top of each other, as the Navigator does, I'm able to get back to the home page from any slide.

The implementation is very simple, I just have a list of slides defined in a static mapping and in this way I can build them programmatically.

This is my mapping:

List<List<String>> pages = [
  ['assets/images/Cover.png', 'Hector the little dinosaur', ''],
  [
    'assets/images/page1.png',
    """Hector is a little dinosaur who lives in the forest.
He spends all his days eating flowers and having a rest.""",
    'assets/audios/page1.mp3',
  ],
  ...
]

Well done Flutter having this implemented is a big step forward towards the goal of publishing my children's book¹ app!²

Hector the little dinosaur written and illustrated by Aurelie Mercier. Cover image is also part of the book. ↩
As usual thanks to Peter for the few english corrections here and there, apparently I'm even getting better with my english 💪. ↩

Typescript or Dart? And More Important, React or Flutter?

Daniele Bertella — Wed, 13 May 2020 08:10:48 +0000

This is the second part of a series of articles I want to write about my first attempt to build a children's book¹ adapted as mobile app in Flutter . If you didn't read the first part you can find it here.

My intention is not to dive deep into technical details but to give a fair comparison of the developer experience of these two worlds: React + TypeScript vs Flutter + Dart.

I'm sure many people wrote about it already but I think it's still worth iteration. If you are like me, a web developer, and you are planning to write your next app in Flutter at least you know what you're up against.

Components vs Widgets

This is going to be the first battle: in Flutter we have Widgets which are very similar to old school React components. It's good that at least they made the new keyword optional in Dart, thus instantiating a class would feel like calling a function 🥶 (You could find many examples online written in the old style though.) Either way, this syntax still looks quite ugly in my opinion.

Parenthesis, commas, and semicolons are all over the place.

A simple widget can end up this way very easily in my very little experience:

Align(
  alignment: Alignment.topCenter,
  child: Padding(
    padding: const EdgeInsets.all(8.0),
    child: Container(
      decoration: BoxDecoration(
        borderRadius: BorderRadius.circular(10),
        color: Colors.white.withOpacity(0.9),
      ),
      child: Padding(
        padding: EdgeInsets.all(12.0),
        child: Text(
          text,
          textAlign: TextAlign.center,
          style: GoogleFonts.walterTurncoat(
            fontSize: 16.0,
            fontWeight: FontWeight.bold,
            color: Colors.blueGrey, // Color(0xff185122),
          ),
        ), // Text
      ), // Padding
    ), // Container
  ), // Padding
); // Align

This is not a complete widget you need to declare a class around it. It's just its content, what we return. Basically this is what one would write in JSX if this was written using React. When JSX was introduced people where skeptical. I believe having an HTML-like syntax with opening and closing tags is easier to read and understand and it's quite difficult to come up with something better than that.

In this case vscode is nice enough to add those smart comments after every closing parenthesis indicating what it's matching. Yet it's not the same.
Don't even get me started on the commas and semicolons!

Fragments in React are a very good feature that helps you write less and keep your code more maintainable. JSX FTW!

On the plus I like the way in Flutter widgets are super specialized. Some accept a single child, some a list of children for example.

There is a Padding widget and its only purpose is to wrap an element and add a padding around or inside it. Another example is the Opacity one but really all of them have a single responsibility. Leveraging this concept I believe it will help you write better React apps after all.

There is a lot of documentation about the different widgets and it's very easy to find the right one to use. StackOverflow is your friend here, as always, but the autocompletion in vscode is amazing so you might be able to find what you need without leaving your text editor.

I spent more or less two days googoling how to do bits and pieces and I was able to find what I needed quite easily.

Stateful or Stateless

As far as I know you have two types of Widgets: Stateful and Sateless:

class MyPageView extends StatefulWidget {
  MyPageView({Key key}) : super(key: key);

  _MyPageViewState createState() => _MyPageViewState();
}

In the example above we are missing the whole implementation that is in _MyPageViewState class. If you want to see what happens next have a look at the repository where this snippets are taken from.

class PageSlide extends StatelessWidget {
  final String path;
  final String text;

  PageSlide({
    @required this.path,
    @required this.text,
  });

  @override
  Widget build(BuildContext context) { ... }
}

And this is a stateless one. Pretty straight forward, right? Also you will have a lot of help from your editor of choice in building the constructor with the required parameters for example or if you forget to add @override, etc.
The fact that Dart is a real statically typed language brings a lot of powerful tooling opportunity to the table and the compiler is there to help you along the way.

Does this ring any bells? To me it looks very similar to what React was a year ago: class components with lifecycle and state vs plain functional components, doesn't it?

Classes why classes?

This brings me to the thing I miss most from React. The hooks! They made such a wonderful job there and wiped out the needs to use classes. In Flutter classes are the way to go, everything seems to be a class. I really don't like this, but there's no other way around it.

Conclusion

I'll wrap it up because I also want to write some code tonight and I don't want this post to be too long anyway.

I don't think anything could move me away from React (and Typescript and JSX) anytime soon. I'm totally into it and I'm enjoying writing it on a daily basis.

But hey, something else is out there, it's nice to discover a new world and figure out why people liked it. I'm interested in seeing if there is something worth to learn from it, in order to make myself a better dev.

I'm really enjoying working with Flutter so far. I want to publish my first app soon. Let's see if I can accomplish this!²

Hector the little dinosaur written and illustrated by Aurelie Mercier. Cover image is also part of the book. ↩
Once again thanks Peter for being patient with me and proof reading all my posts! 😘 ↩

Wrapping my Head Around Flutter

Daniele Bertella — Tue, 12 May 2020 10:43:27 +0000

Disclaimer: I'm a frontend (web) developer, with no experience in native mobile applications and I'm using mainly React from the last 5 years at least. I have a little experience with React Native but that was a long time ago and I have mixed feelings about it.

Also this is my first real experience outside the JavaScript world apart from a little excursus on Rust¹ and a very, very little one in C# and Unity.

Writing React all day has been a breeze for me. Although, it made me lazy and I wasn't so keen to change my usual developer experience.

That was up to two days ago when I started writing this simple application.
Hector the little dinosaur (the website is built in Gatsby btw) a book written and illustrated by Aurelie Mercier.

So what I want to build is basically a slideshow of the illustrations of the book with the text on top of them (I wanted to put it at the bottom but unfortunately the drawings don't always play well with that layout).

Then came the idea: why not recording my 4yo "reading" the book? I could turn the app into an audiobook with a cute, little kid's voice reading the story for you. Awesome, I'm totally sold. Let's start!

Candidates Flutter vs React Native.

As I mentioned before React Native would have probably been in my comfort zone but, hey, I tried it and I didn't fall in love with it that time.

Flutter, yeah, let's try something new! There was a lot of hype around it coming from real mobile devs, so why not? Let's do it properly!

I decided not to take any tutorials, I just ran through the installation process, and started my first project. It felt a bit frustrating at first, I needed to install Xcode and a lot of other stuff (and I didn't even set up android yet!) but I was up and running in a couple of hours, maybe even less.

I opened the project and... I didn't like what I was looking at!
Classes, classes everywhere 🙀! The parentheses, commas and semicolons didn't help either!

I'm so used to React and its nice hooks-API that I forgot what's a class is actually useful for.
I honestly turn it off straight away.

Until next day and the next post!

If you are curious about what will happen next here is what I want to write about:

Comparison between React/Ts and Flutter/Dart
Pain points on this ongoing development
Publishing the app (I hope I will get there at some point)

If you are curious to follow the ongoing process have a look at the repository github.com/dbertella/hector-app and feel free to drop a comment if you notice something wrong 😘

A huge thanks to my friend Peter for trying to teach me this fabulous language. And thanks for correcting my english too! ↩

DEV Community: Daniele Bertella

Gatsby or not Gatsby. What's Next 😍?

Next.js

getStaticProps (Static Generation) 🔗

getStaticPaths (Static Generation) 🔗

getServerSideProps (Server-side Rendering) 🔗

Not everything is 💅

Conclusion

Publishing my Flutter App on Google Play Store

May the 27th: App live for the first time!

Jun the 4th: Public Beta!

Jun the 9th: Pushing the red button 🚨

Jun the 10th: The app is live

That was definitely the beginning of a beautiful friendship!

Time to Publish my First Flutter App on the Play Store (a Week After)

Time to Publish my First Flutter App on the Store!

The day to publish the app came 👊

Icons and Splash screen

Build the app for release 💣

Sign up for a developer account 💸

Conclusion 🍕

What I Really Like About Flutter so Far

Everything just works! 🤘

A Super Cli 🔥

VS Code integration 👀

Native feeling 🤞

Wrapping it up 💣

Add a Navigator to a Flutter App

The Story Widget

Typescript or Dart? And More Important, React or Flutter?

Components vs Widgets

Stateful or Stateless

Classes why classes?

Conclusion

Wrapping my Head Around Flutter

`getStaticProps` (Static Generation) 🔗

`getStaticPaths` (Static Generation) 🔗

`getServerSideProps` (Server-side Rendering) 🔗

That was `definitely` the beginning of a beautiful friendship!