My experience with XE 5 and android not so good parts:

My experience with XE 5 and android not so good parts:
1. When u press run, to slow to see result on emulator or android device.
2. Hello world is like 5-6MB, comparing with eclipse where is my application 124 KB with database.
3.U can use only on new android devices cause u need NEON capabilities, like on Tegra 3 +.
Embarcadero forgot to tell us on their delphi-android videos if u planing to start your application on android VM u must check 'Use Host GPU'

Comments

  1. android emulators were dead slow last time I've tested, I'd go for testing on a real device...

    ReplyDelete
  2. 2. Take better look at the device - 5-6Mb - is compressed size - but on device it will be more 20Mb, then app done by ecliple still will not more then 1mb :(

    ReplyDelete
  3. For hello world Delphi is not the better solution but making more complex designs I have frankly impressed with firemonkey for Android.

    ReplyDelete
  4. Francisco, this is HUGE step for delphi with firemonkey, waiting for this from XE 2. And I agree that u can make rly complex design easy. But if hello world is 5-6 MB, in samples/ firemonkeyMobile u can find TabledMasterDetail example. Litle more then hello world, u have one listview on left side with couple pictures and like20-30 users, detailview on right side not to much complex but nice looking and that app is 9MB. I think thats to much. I belive that they will fix that, but for now I cant use that :(

    ReplyDelete
  5. Drazen Djurisic I agree with you. We just arrived in the android platform and we have a lot of work. we can't make background services, we can't make widgets and there are some limitatiins with hardware. But the more complex stuff is done. But the result is promissing. I haven't used delphi for ios but firemonkey in my s4 works really really good.

    ReplyDelete
  6. I don't really care about the size, even most phones now have a pretty decent storage. But it does take a while to compile and open on the device, that could still use some improvements.

    ReplyDelete
  7. There is an interesting article that may help you solve the slow emulator part of your problem ;-)
    http://www.tmssoftware.com/site/blog.asp?post=273

    ReplyDelete
  8. Fabio VITALE Looks like "Bruno from tms" adressed his post not for Delphi developers, because in our world Delphi for Android produce only ARM binaries (not x86) which will NOT work on Intel HAXM emulator solution!
    From artice he posted:
    The Intel HAX driver will only work for Atom based Android emulator images.
    Looks like he didn't even read it, or if he did it, so his post looks like mockery for delphi users.......

    ReplyDelete
  9. I suspect all those who are complaining about app size started programming in Turbo Pascal. In those days app size was important; now, within reason, it's irrelevant.

    ReplyDelete
  10. Not yet irrelevant on a phone with 1Gb RAM. And, the firemonkey apps already have issues with startup time.

    ReplyDelete
  11. Regarding Use Host GPU setting, it's properly documented in the product documentation:

    http://docwiki.embarcadero.com/RADStudio/XE5/en/Creating_an_Android_Emulator

    ReplyDelete
  12. Lars Fosdal for me the startup time is the first relevant and apreciable element to resolve to bring a "Native performance" perception

    ReplyDelete
  13. Bloat is never irrelevant. In many cases, I saw faster performance from D2 on Win2K that I see now from DXE on Win7. And the difference in app size is huge. Given a processor clock speed ratio of 17:1 (and even ignoring single core vs. HT quad core,) that's very sad.

    ReplyDelete
  14. Xe5 seems to improve on the weight of the created executable.

    My test program firemonkey under xe3 weighed 8500ko, it makes more 4500ko with Xe5, in both cases in mode release.

    Confirm with other projects, but it is a good point

    ReplyDelete

Post a Comment