+1, it's definitely best option.

That said, we're building consumer-facing apps where long-term stability is critical. Our goal is to build once and run on any platform, across versions. Most consumers are already tied to existing platforms that provide services we can't easily replicate, which makes development of apps in a new OS or In a OS look like environment is a tough sell.

I must follow same technical mechanism as Java.

I joked. You should use Java. Few companies have the resources to duplicate Java and the JVM in a reasonable time. At this point Java and the JVM have three decades and tens of thousands of developers backing them up.

Thanks, Anyway I took it serious. I'll decide.

Why not just use Java then? There's an unbelievable amount of open source work you can leverage

Java apps are easy to decompile and API details will be accessed. Because of decompilation of source code other companies can easily repack our codes and change the brand.

I did same hack and rebranded then sold. That's the main concern. Anyways, we are thinking to go with system WebViews. It's still interpreted but requires some hard time.