iOS support planning

[songyiYu]

iOS has similar function named 'Widget'.

It feels like sticky notification.

[yenoss]

Yes, ios support is hard.

There are several ways to create a persistent notification.

One of them is to use local notification.
However, you can't keep local notifications indefinitely-you can't set certain notifications at will, and it's impossible to keep them in the statusbar all the time.

Another way is to use widgets.
But providing widgets through the flutter platform is a whole different story.

First, widgets are processes that have areas that are independent of the application.
That is, memory is allocated separately. Functionally, you can load data through the api from the parent application. However, you can't put information directly with flutter native functions. You will have to write code with a bad design, such as using internal in-memory storage.

The second reason is that drawing the widget's screen is not easy.
To make a widget a flutter plugin, you need to draw the widget programmically. It is not easy to display the screen through simple flutter functions.
As you know, most of flutter's UI plugins are implemented with dart.

flutter needs to support native platform view more strongly, or the widget itself should behave like an ios based library. (Just like google map)

I think the above reasons make ios support difficult.

But if anyone has a better idea, please comment on the issue here.