harmonyOs next

[tjiakwokyung28]

https://www.huaweicentral.com/harmonyos-next-breaks-android-ios-duopoly-in-os-field-says-huawei/

harmonyOs have more than 7.2 million developers joined the ecosystem, and over 1 billion devices installed the OS.

what about tizen supported by maui? microsoft should not make another wrong move like taking over nokia. maui must be able to run on harmonyOs, before it's too late

[true-perfect-code]

Support of Harmony OS would definitely make sense, but I would prefer MAUI stability at this moment.

Regards
pc

[cjrvdev]

MAUI struggles to be up to date with "new" google policies in many of their tools (like Essentials) and stopped supporting useful libraries like Firebase. Do you really expect them to support more ecosystems when this one is barely holding up?
(with all my respects to MS team, which Im aware many are trying really hard)

[true-perfect-code]

I have already commented on this in an article. The real problem is the MS C-suite, which makes strategic decisions but does not communicate them to the outside world. For example, none of us (including the MAUI team) don't even know whether MAUI is being run as a microsoft hobby project? Because the question comes up why Microsoft did not start to convert their own products to MAUI when MAUI was released?

@cjrvdev
I am very confused about the “new” google policies. What is the status there in MAUI and do we have to prepare ourselves for the fact that our time invested in the development of MAUI apps is in vain because none can currently be published on the Google Store now?

[cjrvdev]

Well at this moment the policy about removing read storage (and the other 2 variations) is days away. And products like MAUI essentials media picker for android still have no support for it (although a cool buddy shared some code which works great btw). They are also using the write storage permission incorrectly as per android docs (it no longer exists if you target api 30 and above).
Contacts API is also very outdated and using a very bad performance approach and hasn't been updated. It was commented a long time ago in Xamarin Essentials old repo and wanted to revisit it at some point which has never arrived.

Honestly Im worried about MAUI's future as Android now enters a faster release cycle which will most likely enforce new play store policies and stuff... Unless MS really sits down and goes full blast into mobile development the newer tools like KMP/Compose MP will definitely deal the final blow...

[true-perfect-code]

To be fair, I look for MAUI alternatives at least once a month because of basic MAUI/VS 2022 problems (see e.g. my post here about local windows notification, publish etc.).

Basically only Blazor is important to me because I've been working with it since the release and am very happy with it (stability, performance etc.). However, I would like to write apps for all platforms, not just for the web. When MAUI came out with Blazor, it was a real Christmas present for me :)

In the meantime, there are also other frameworks that should support Blazor: Electron NET and UNO. What worries me there too is that you can't read much about it at the moment and it also raises the question for me whether I will replace one evil (MAUI) with a second evil by switching to Electron/UNO?

Can you say anything about UNO/Electron NET (for comparison with MAUI, platform stability on Android/iOS and support)? Or are you familiar with other alternatives in which I could also use Blazor?

Thanks

[cjrvdev]

Well Im not really into web/desktop development unfortunately so I cant really give you a good suggestion. UNO and Electron I've always heard are pretty good and stable. Electron might have worse performance I think but there are many apps like SourceTree using it and you can tell by yourself they are quite good.

Cheers!

[true-perfect-code]

@cjrvdev

With uno I don't like the fact that you have to use XAML. I have been using XAML for over 10 years, even now, but I find many disadvantages compared to Razor (Blazor).

As far as I know, you can't program mobile with Electron / Electron NET.

My conclusion is that MAUI really has a huge potential, because you can program both frontend and backend with one language, and if it needs JS, you can use it too (I'm talking about MAUI Blazor + Blazow Web).

We probably have a few million developers who, like me, create apps for Windows professionally (be it in Winforms or WPF), so C# and NET is our daily work. The step to have an app with one code then on all possible platforms would be really small with MAUI, if MAUI would be ready for production use. that's really a pity, because I think MAUI would be the most popular framework.

pc

[giuseppenovielli]

#15536 (comment)
#15536 (comment)

https://harmonyoshub.com/net-support-is-coming-to-openharmony-in-the-form-of-third-party-library-by-the-open-source-community/

[tjiakwokyung28]

look at the development of Huawei technology, net maui must be able to run quickly on harmonyOs next, rather than to ios whose innovation development is slow, or tizen which has no users. net maui is a good product, it's just a shame it's not multi-platform because it can't run on harmonyos, if it is truly multi-platform, including running on harmony os in the future net maui will be number one

https://www.facebook.com/share/v/15ZEDgLVyy/?mibextid=wwXIfr

[true-perfect-code]

@tjiakwokyung28

MAUI support for “HarmonyOS Next” would of course make sense, but currently we have fundamental problems in MAUI in all directions (infrastructure, stability, recurring bugs, coordination with other MS teams etc.).

I see the cause in a very small number of programmers (probably because MS is saving money here). This also makes the question of MAUI support for “HarmonyOS Next” superfluous, no matter how tempting it sounds.

But I would summarize it like this:
Let's get MAUI to a stability level first, so that programmers can use MAUI professionally first. At the moment I personally believe that there is not a single programmer out there who would recommend MAUI to a customer and that is a big problem at the moment because MAUI is just a very expensive hobby (for example, I lost over 10 hours of my vacation last week alone because I was writing and testing back and forth via the local notification in MAUI Windows and Programmers who do this in other frameworks would laugh at MAUI).

By the way, I have read a bit about “HarmonyOS Next” and I have to admit that I am not really happy about it. For example, starting from IDE (DevEco Studio is proprietary) to the programming language ArkTS (subset of TypeScript), availability only in China, and the thing that bothers me personally the most about UI is that you deviate from HTML/CSS (like Flutter). I would have hoped that everyone would have learned from the example of Microsoft that proprietary paths lead to a dead end.

Regards
pc

[tjiakwokyung28]

I tried migrating to xamarin then to maui, after spending money, time in making software turned out to be a hobby with microsoft products, not for professionals, you could say as a tester, crazy every few days maui updates, in our code so bugs appear here and there, now we better wait until the bugs are minimal, then we develop software again with maui. while waiting and not wasting much time I turned to animation with autodesk maya, in order to get money. from my experience using maui, this product is good and many things in mobile applications that cannot be made with python, fluter, java script, can be made with maui. it's just a shame there are so many bugs. for the maui interface display should use coef for example the standard maui display is a, if running on an iphoneX becomes (the iphone coef) x (the maui standard), if running on windows with a 19 inch monitor= (the size becomes the win coef 19) x (the maui standard), and so on. this will reduce the level of bugs on the multi platform maui