1.0 Roadmap

[SaltyAom]

1.0 Roadmap

Flutter is great.

It's easy, performant and run-on every platform.

However, there's still some complexity in Flutter itself.

As I want to encourage every developer to try out Flutter, I create Niku.

Niku help to resolve the Nested Hell problem in Flutter.

By composing Widget's styling to be easy to read and more maintainable.

Before I released, Niku 1. I want to make sure that every aspect of Niku is met.

Niku should be:

• Resolve Nested Hell in Flutter.
• Easy, maintainable and idoimatic to Flutter.
• High performance as close as native Flutter.
• Low learning curve and adopatable everywhere.
• It just work.

Before 1.0 is released, I want to make sure that everything is perfect.
I want to lay solid foundation of Niku first, before moving further.

The vision for current stage before version 1.0 is released is

Roadmap:

• New Type Niku
• Unit Test
• Web Documentation

New Type Niku

Writing build() every time we use Niku Widget is annoying. We want to focus on styling. Not on non-sense transformation method.

That's why there's Niku NT.

Niku NT or Niku New Type is a new implementation of Niku based on mutable StatelessWidget.
Previously, Niku is based on Niku class which required to transform into Widget every time.
That's why we need to call build() every time Widget is written.

Version Zero Niku:

NT Niku:

Instead of using dot notation, NT will use Cascade notation instead.
This is performance best practice of Dart.
By doing this, instead of returning this (instance) every time, we let Dart mutate internal property instead of returning new instance.

This also resolve Niku Widget Stack memory performance as everytime dot-notation is called on base Niku property, as there's no stack anymore.

The worst possible Time Complexity of building Niku widget is reduced from O(n + 1) to O(2).
As there's no new instance to be construct, no build method need to be called for every stack anymore.

This will help achive near native Flutter performance when using Niku.

Unit Test

I want every developer to put their idea to Niku.
But without Unit Test, there's no check and we have to manually test library everytime your contribution.

Before ther released of Niku 1.0, I want to make sure that every developer could contribute to Niku without any worry.

We would love to see what you'll help Flutter developer to develope their platform.

Web Documentation

I come from web development background, I want to ensure that every developer that would like to learn Niku will have a great experience.

That's why I want to create a proper documentation before releasing 1.0.

That roadmap for web documentation is:

• Good explaination
• Explain core concept and every property detail
• Searchable
• Clear section seperation
• Easy navigation
• Performance and work on every browser

I plan to do it in Preact and Next.js, but that's after every foundation is solid.

Afterword

There's no clear data of released yet, but I plan to released 1.0 before end of Q2 of 2021.