Skip to main content
June 15, 2011
Question

Two questions (preloader and unique id)

  • June 15, 2011
  • 3 replies
  • 888 views

Hi there,

I have two questions for you.

1) I have read (and experienced directly) the problem that Air Android apps have no chance to show a splash screen to the user when the app is loading.

This is a bad thing because the user has no feedback that something is happening and if the app is big he only see a black screen for some time.

What then if I split my application in two swf like the web based ones?

I mean to have a small preloader.swf (that is my main android app) that shows a splash screen to the user while it loads a application.swf (that is the biggest part of the app)

What exactly happens at runtime?

I ask because I've read somewhere that the starting latency depends not only by the loading time of the entire apk but also the air runtime tooks some time in instantiating the swf: so if I split it in two maybe it goes faster because it has to instantiate a smaller swf (then it tooks some time to instantiate the other swf but I don't care because the smaller swf showed to the user the splash screen so the user has a feedback that something is happening)

2) Is there a way to obtain an unique id of the phone where the app is running?

Thanks in advance

This topic is closed to new replies. Start a new post to keep the conversation going.

3 replies

relaxatraja
Inspiring
June 15, 2011

Here is a demo for using splash screen on mobile applications

http://swfhead.com/blog/?p=817

Participating Frequently
June 15, 2011

Hello,

as to 1) see that thread (yes, people use different .swf to add splash on Android):

http://forums.adobe.com/message/3713982

as to 2) Iv'e read that there is UUID access via BlackBerry iOS additions to Air SDK:

http://forums.adobe.com/message/3736557

- but not on Android/iOS as that is (access to uuid of device) not part of SDK/runtime

regards,

Peter

Participating Frequently
June 15, 2011

For #2, this is more problematic than it probably should be, even for native Android apps. Google recommends creating and storing your own unique ID number to track installations rather than devices.

Some threads on the topic:

http://android-developers.blogspot.com/2011/03/identifying-app-installations.html

http://stackoverflow.com/questions/2785485/is-there-a-unique-android-device-id