During the second half of 2020, the Flutter team introduced a revamped navigation and routing system called Navigator 2.0. The reception by the developer community has not been great so far: principal criticisms regard the API complexity and the absence of an extra abstraction layer for common scenarios.
In a previous article I discussed about freezed and kt_dart, a couple of packages that bring immutable value types to Dart and Flutter. I omitted to cover a free feature exposed by freezed: the integration with json_serialializable.
First of all, add the dependency to pubspec.yaml file:
Then, edit your…
I’m not too convinced that cross-platform UI will ever be a real thing in terms of final product quality (btw, I think a real thing might be Kotlin Multiplatform logic + native UI layer), nobody can doubt that tools like Flutter or React Native are really effective if we talk…
First things first: what is Next.js?
A small framework for server-rendered universal JavaScript webapps, built on top of React, Webpack and Babel.
It comes out of the box with preconfigured features like routing, static optimization, server-side rendering, code splitting, CSS-in-JS support, hot reloading and API routes à la Express.js,
I was reading again my article about Jetpack Navigation, in particular the part regarding the parameters passed to destinations. I can pass small serializable objects, but what can I do to pass more complex stateful objects?
When you navigate to a destination, a fragment is automatically instantiated with direction parameters…
From an iOS developer perspective, how screens are presented in an Android is quite strange. The first time I developed an Android app, I was taught to create an Activity per screenful of content. Then, they have introduced me to Fragments, at the same time warning me about their cumbersome…
In previous episode I introduced code splitting without adding any feature. Now it’s time to move on and to code an header component with logo, title and navigation commands.
It is useful to create a general layout component to make sure every screen have same UI structure.
In previous episode we introduced routing. App starts to have a structure: I’ll try to run a production build to evaluate code size.
$ npm run build
In previous episode I structured my React app using composition of components. Now it’s time to adopt react-router to go from poll list to single poll where user will vote.
$ npm install --save react-router-dom
$ npm install --save-dev @types/react-router-domFirebase hosting is already configured to support browser history thanks…
