[android-developers] Digest for android-developers@googlegroups.com - 3 updates in 2 topics

jtoolsdev <brianjtools@gmail.com>: Mar 21 03:25PM -0700

Really? If you know Android programming then HTML5 and Javascript should
be a piece of cake. And you probably don't need much knowledge of that to
change the example for your app. You can set up a server on your machine
to test. There's this thing called Google where you can search for that
info. Maybe you can use Github too. I think the example explains how to
do that but I just used my own web site.
 
Just knowing Android programming is not going to help you survive in the
tech world.
 
On Friday, March 20, 2015 at 4:23:01 AM UTC-7, saex wrote:
Guy Smith <guy@multiniche.org>: Mar 21 12:31AM -0700

My twopence worth... as a hobby app developer, my main concern is a
platform that puts up as few obstacles as possible.
 
I loathe "version hell": the code works under this version, but breaks
under that version ; the display is fine on most screens but breaks on
particular sizes ; yada yada.
 
Any cross-platform SDK has to sit on top of all these versions, from each
of Apple, Android, Microsoft, perhaps all the browser APIs if you're doing
web-enabled stuff, and any other random companies (Ubuntu, Samsung?) that
bring out a mobile platform.
 
Somewhere, you are going to have to make a trade-off. On some aspect,
you're going to be way behind the single platform SDKs. It might be
performance, complexity, features, robustness, whatever, but it's going to
be something.
 
Who do you expect to use your platform? For example, governments would want
to develop cross-platform apps as cheaply as possible and don't care about
performance or robustness, game developers probably care about performance,
retailers probably care about look&feel and robustness.
 
 
On Saturday, March 21, 2015 at 11:39:26 AM UTC+10, Mario Zechner wrote:
Mario Zechner <badlogicgames@gmail.com>: Mar 21 02:59AM -0700

Great input, thanks! As you said, with a cross-platform UI solution, there will always be platform/OEM/device specific issues that need special care. We can solve a lot of these on our end. There will obviously be cases we can't anticipate. The take away for me here is, that it should be possible for developers to easily special case in such a scenario. E.g. use the cross-platform API for 80% of the app, mix it with native APIs where necessary.
 
As for our target. Atm Android developers who want to expand to iOS more easily as well as Android/iOS devs who already do both platforms but want to unify their tooling and share code across platforms are our target. In terms of type of apps, we want to cover all the bases. Game Dev is already covered (via libGDX) with great success. Retailers are also covered, they can use the native APIs on each platform to get 100% native UX, while sharing business logic between platforms. Governmental and enterprise is what we currently are working on and at which my initial questions are aimed.
 
Thanks for the input, really appreciated!
You received this digest because you're subscribed to updates for this group. You can change your settings on the group membership page.
To unsubscribe from this group and stop receiving emails from it send an email to android-developers+unsubscribe@googlegroups.com.

No comments:

Post a Comment