Next week I will be publishing a Medium article, w...

# multiplatform

[Daniele B]

Next week I will be publishing a Medium article, where I will summarize my 6-month research into DeclarativeUIs and Kotlin MultiPlatform, connected via the MVI pattern.
This diagram is a preview. Next week I will be linking the full article, with more details about the overall architecture.
These are paragraphs of the article I am writing:
- The Past
- The Future
- The 3 pillars for the future of apps
- The D-KMP architecture
- Declarative UIs have landed on Android and iOS!
- Why declarative UIs?
- Kotlin 1.4 has made MultiPlatform real!
- Why Kotlin MultiPlatform is the future?
- KMP vs Flutter vs ReactNative
- Platform-specific code in D-KMP is just 15%
- MVI pattern: the third pillar of D-KMP
- StateFlow: the MVI pattern enabler on KMP
- StateFlow on the different platforms
- Rich client vs Thin client
- Multi-Platform: why Kotlin and not Swift?
- Team organization
- The legacies
- KMP libraries
- D-KMP for Web

[Kris Wong]

that sounds like a very long article. I would recommend breaking it down into 3 or 4.

[Daniele B]

it should be around 15 mins long, according to Medium

[Robert Jaros]

What is D-KMP?

[Daniele B]

It’s the name given to the architecture which will be described in the article, based on these 3 pillars:
• DeclarativeUIs
• Kotlin MultiPlatform
• MVI pattern

[Daniele B]

here is a diagram

[Robert Jaros]

As for the web part - it would be nice to mention, Kotlin React is not the only way for declarative/reactive UI for the web 🙂 Both KVision and Fritz2 also support this pattern. But that's just my three cents 🙂

[Daniele B]

What we are looking forward to is actually JetpackCompose for the Web, which we hope will appear sometime in 2021.
But in the meantime, we rely on the declarative-UI web framework which is best supported by Kotlin at the moment: React.

[Kris Wong]

yeah 15 min should be split into 3 articles

[Kris Wong]

or no one will read the whole thing

[Daniele B]

I am thinking to present the paragraph summary (the one I also posted here) at the top of the article, so that the reader can be aware from the beginning which are the topics and can go directly to the section they are most interested in, if they wish.

[Daniele B]

Maybe it’s just a matter of taste. I personally feel overwhelmed when I am presented with an article that is just the first of a series, and I am not fully aware what the next articles will talk about. I need to have a very big motivation to start reading the first article of a series.
I feel better if I am aware from the beginning what all the topics of the article are, and I guess I don’t mind that they are all on one page.
But thanks for the suggestion. After I finish writing, I will consider if it makes sense to split it in 2 articles, by still keeping the full list of paragraph titles at the top of both articles.

[Kris Wong]

you do you. i'm just speaking from experience.

[Daniele B]

Thanks 👍

[andylamax]

I am so looking forward to this. But again if it too long, very few of us will read it

[Daniele B]

@andylamax thanks for the interest. Do you think splitting the content in multiple articles will help, or do you think that long content in general (either in 1 long article or in multiple smaller articles) will receive less attention in any case?

[andylamax]

I think split it in multiple parts, and if you can publish them all at once with links pointing to one another

[andylamax]

That way, one can read one part. Do their things and also catch on the next part after

[andylamax]

Plus I believe it will make a good flow to it. Gives you few sections to concentrate on per each part

[Daniele B]

thanks 👍

[zsperske]

Looking forward to this as well!