(1) If we use multiple screen than we need lase block per screen.
(2) If we use method to reduce screen size than we need to put more blocks on each screen..
Which part can do more effect on slow app speed, Multiple screen or More Blocks per screen..
(Please ignore that app inventor working better with maximum 10 screen.)
Most probably no one has tested the scenarios you mention.
What happens with speed of execution probably would be highly influenced by:
1) Android device system memory ... if the device has a lot, a single screen might be 'faster' (whatever that means) then using several screens with less components each of which would use less system memory. If system memory is a limiting factor, probably more screens is the answer (and definitely less then ten screens).
2 Android processor speed and version of Android ...what hardware the device running the app will influence how 'fast' the app responds. A well designed single screen app might run faster or slower than multiple screens. This is probably highly dependent on what Controls are used. Math operations in AI2 are relatively slow as are screen refreshes and drawing to the Canvas compared to the speed with which other controls execute (in my opinion..without no comparison tests). A sort routine takes seconds in AI2 block code but ms in java script.
3) Running in an emulator or a device.... the device always wins, however if you are in live development mode, this might be a toss-up.
4) I expect any well designed Eclipse or Android Studio app will outperform any AI2 app ... maybe I am wrong however because AI2 uses several different platforms to process information, it is probably inherently slower that Java compiled apps.
The above is just my speculation; others might have other opinions. Perhaps one of the Development Team will have some comment.
Run some tests, report back and become an App Inventor Hero and Experimenter!
댓글 없음:
댓글 쓰기