DEV Community

loading...

Discussion on: Introducing MobileUI

Collapse
kristijanfistrek profile image
KristijanFištrek

Really interesting and amazing product, congratulations!

I have to ask, in lamest terms, could you explain why would someone choose your product over Ionic/Angular Native and similar? What are some of the advantages?

Collapse
henrikwirth profile image
Henrik Wirth Author

There surely will be some more articles coming up, explaining certain aspects of the framework and how they compare to other frameworks.

That being said, I'd say some of the biggest advantages are:

  • You can stay in one language/environment, even if you need to build your own abstractions. No need for Swift or Objective-C etc.
  • You can make use of the massive amount of well written Java/Kotlin libraries.
  • Native performance and look and feel
  • For agencies: There are a lot of Java developers out there

Obviously it's a difficult market to compete, but we are confident in the developer experience of our product. We enjoy building apps with it a lot.

Hope you give it a try and have us some feedback. Always happy to improve things.

Collapse
dthommes profile image
Dr. Daniel Thommes • Edited

Hey Kristijan,

that's a great question. Surely, there are a ton of pros and cons when we are talking about cross-platform today. With MobileUI, our main goals are:

  1. Enable developers to build apps with great quality. This typically means: The framework must support native UI as this typically resembles the great look and feel your users love from all the competing apps on their phones. Users get the full FPS from the UI (e.g. for animations), super-fast response times and they can use the gestures they love (e.g. for navigation).

  2. Save time and effort by going cross-platform. While the above is all great, one could achieve this with dual-development for Android and iOS as well. This is okay, if you have the budget. But going cross-platform typically brings significant savings. That's why MobileUI is a cross-platform approach. But with an important addition: You can also break out of the "single codebase" whenever needed. With MobileUI running on Android Runtime and RoboVM, you have the possibility to directly access native SDKs from Java and Kotlin. And that's a main difference to Ionic, React Native or Flutter, where you need to switch languages, tools and IDEs to implement native extensions.

But for sure, we are also big fans of the Java and Kotlin ecosystem. And with us are about 9 million Java developers and millions of Android devs. MobileUI enables them to build amazing cross platform apps. Especially for Android developers, we give our best to flatten the learning curve 😁. And that's what makes it easy for agencies and companies that have Android developers to go cross-platform!