Sorry Embarcadero you are great with WINDOW

Sorry Embarcadero you are great with WINDOW
but on Android..
I Started investigation ,for a project, a piece of code
for Android just a few lines of code <50.
On window it runs great, but
On Android waaa.. bad bad.

1. The size 40G i can not run it on S2 (luck of memory) only on S6.
2. Behavior bad.
3. How do you Ebaracdero expect a professional user to work ?
4. Do i research on each pies of code ? wast of time.

same exact project with Android Studio
1. The size 780k!!
2. run as expected.

I love Delphi and its IDE using it since #1 but it seem
i will not use it for Android.
I mite be wrong ,i will keep trying.

P.S I made all ready a project for Android with Delphi
and it works Ok but once started on a new
one well... cannot go beyond investigation.

To sum it up Delphi is much better , then Android Studio , for designing
a project but it lucks the 100% result.

Comments

  1. Shouldn't that better belong into Delphi Code Rants instead of Delphi Feature Requests?

    ReplyDelete
  2. Uwe Raabe I did not know where to add my frustration . Feature -maybe ,maybe some one at Embaracadero will wake up and the feature to make Delphi for Android much better

    ReplyDelete
  3. Im not sure I understand everything you are saying Shlomo, with S2 are you talking about the Samsung Galaxy S2? If so, that is definitively outdated. I think that was out around the same time as Apple iPhone 3GS (?) which is ancient compared to the average phone today.

    You also mention 40g? If you are saying that your binary compiles to 40 gigabyte from just a few lines of code, then there is something seriously wrong with your setup.

    As for Android Studio, that compiles to bytecodes (unless you explicitly define native pre-compilation) which is then converted to native on the device. Android was initially made in Java so that will obviously have an advantage there.

    But please clarify phone model, Delphi version, the "small code" snippet you are using -and above all, what mobile brand and model you are using.

    ReplyDelete
  4. shlomo abuisak FMX is a bit heavy, but Delphi can build tiny Android Application any way :)

    github.com - Delphi
    (do not compile any more under Tokyo...have to fix that)

    was made under XE5 in only 825Kb
    https://cc.embarcadero.com/Item/29682

    ReplyDelete
  5. Paul TOTH Is it because you have only DPR? and Lennart Aasenden my problem is not the phone .Program should run on any phone even OLD ! too. The program is too big (that beside the problem) and it dose not run as expected as one has to keep investigating since behavior of the program differ from window to Android, which it should not be for the IDE to be perfect.

    ReplyDelete
  6. Paul TOTH I tried to compile your demo with 10.2.1 and it is missing "pandroid_app" where is it?

    ReplyDelete
  7. Maybe try RemObjects Oxygene approach

    ReplyDelete
  8. shlomo abuisak I don't understand the changes in the Android application logic...I have to dig a bit to fix that :)

    ReplyDelete
  9. Paul TOTH i searched on my computer for pandroid_app and saw on google people did not find it either. I guess it is OLD and Delphi 10.2 dose not use it any more

    ReplyDelete
  10. shlomo abuisak With all respect, I have some pretty old phones here, but I dont expect to target devices more than 5 years backwards. Not even JS developers does that. Although I am conceptually agreeing with you that yes, it should (or would be nice) if it was so, but technology is moving so fast now - it would be somewhat utopia to expect a modern infrastructure to hit a 8-10 year old phone and not run into challenges with the GPU and CPU. But yeah, FMX is top heavy, but sounds like your build is excessive - something must be wrong somewhere.

    ReplyDelete
  11. All opinions regarding old phones notwithstanding, almost 40 megs for a tiny hello world app seems too much.

    ReplyDelete
  12. Is it compiled as Debug or Release? Debug tends to be several times bigger than Release. I don't have a clue regarding yours performance problem.

    ReplyDelete
  13. There are all kinds of ways to address the problem you may be having. You could use https://www.turbococoa.com/ instead of you would like a smaller app that does not use FMX and instead uses Android Studio for the UI. The size of an FMX app does not grow much the more you add. You could have a huge amount of functionality in your app and it will only be 46MB for example. Also you should check out the size of other Android (like Facebook, Snapchat, etc) apps at this point. They are hundreds of MB. Lastly, you kind of have to understand how mobile works regardless which tool you use because Android does not work like Windows. The savings in FireMonkey is in the cross platform capability.

    http://www.firemonkeyx.com/anatomy-of-a-delphi-xe8-firemonkey-app-on-android-ios-windows-and-mac/
    https://plus.google.com/photos/...

    ReplyDelete
  14. A few complex fmx apps work on Samsung galaxy note 2 which is basically s2 with a pen.
    There are stupid apps made in android studio and one on my phone weighs 547mb. As they say bad dancer complains about his balls. And lastly you cannot really leave the place you never ever been to (I don't count hello world).

    ReplyDelete
  15. "... bad dancer complains about his balls ..." what a great adage :-)))

    ReplyDelete
  16. Lol. I find this post very funny. Why are you using an S2 anyway? It's 2018. You shouldn't be using an S2 in 2018. Even S6 is now starting to become too old.

    ReplyDelete
  17. Viggo Jamne Yeah It's so true. If you're an Android developer and you're not targeting Android 8 or higher then there's something wrong. In 2018/2019 you shouldn't target any device lower than Android 8 anymore.

    ReplyDelete
  18. Google has monopoly in Android world, just face it. For example look at this zygote thing - google runtime is already loaded and initialyzed even before android app starts. Just imagine if we could do the same with FMX! But there is no way to do it.

    ReplyDelete
  19. Same was on Windows. Microsoft monopoly. msvcXXX and mfcXXX dlls loaded by many MS apps long before VCL dlls would be.
    But it was not "40G" teported above (hopefully wrongly reported)

    ReplyDelete
  20. Shaun Roselt "In 2018/2019 you shouldn't target any device lower than Android 8 anymore."

    Don't make me smack you with my Samsung Galaxy S5! :-)

    ReplyDelete
  21. Joseph Mitzen You need to upgrade your phone if you develop Android apps. Starting end of September 2018 if I remember correctly then all new Android apps in Google Play Store must target Android 8 and if you update your old apps then they should also now target Android 8. Your apps can still have a lower minimum version, but the target version must be Android 8.0 or higher.

    ReplyDelete

Post a Comment