We have moved to a new Sailfish OS Forum. Please start new discussions there.

Do not hide app cover in the middle of app start process

asked 2013-12-30 01:30:02 +0200

Artem gravatar image

updated 2014-03-11 08:33:21 +0200

ssahla gravatar image

Current app starting sequence seems to be the following:

  1. Show default app cover with "Loading" label
  2. Remove default app cover
  3. Bring app to front
  4. Use whichever cover app wants (probably, you don't see it until app is minimized)

And that is sort of okay except some apps can take time to start. For example, Maps can be particularly slow and sometimes it takes a second or two from the moment Loading app cover is removed till app is shown on screen. Then it totally looks like app failed to start and sometimes I even try starting it again.

Even without so extreme cases whenever there is noticeable app cover removal during app start process it feels like something wrong happened and your context is shuffled for no reason.

edit retag flag offensive close delete

1 Answer

Sort by » oldest newest most voted

answered 2013-12-30 12:49:04 +0200

Removing the cover is intentional I guess: this prevent crashed applications to fill the multitask view. It seems that the launcher don't know the state of the application, so the cover just have a timeout, and after some seconds, the "Loading" cover just dissapears.

Usually, if you are launching an application started with booster, your application should appear directly. Don't do initialization of heavy components during the startup like in the main() function, or Component.onComplete in QML side. Delay them using threads, or Loader so the app will start faster.

edit flag offensive delete publish link more



I suppose Jolla's Maps app should follow all these good practices :) Yet regardless of it, it would be nice if task manager was showing a running as actually running, not as a crashed one.

Artem ( 2013-12-30 13:59:32 +0200 )edit

Well, if the homescreen could detect the state of an app, then it could be nice. The problem is also about the fact that sometimes, showing a window is unrelated to an application running state. Think a CLI application.

Sfiet_Konstantin ( 2013-12-30 14:07:34 +0200 )edit

You clicked an icon in the launcher grid. Some very well known process gets started. We can track whether it's live or not, yes?

Artem ( 2013-12-30 14:27:10 +0200 )edit

Still, if it is a CLI application, what do you do ? Do you display a lauching cover during the whole life of the CLI application ? And what if the CLI application was a daemon ? etc. It is not an easy task ...

Sfiet_Konstantin ( 2013-12-30 14:30:14 +0200 )edit
Login/Signup to Answer

Question tools

1 follower


Asked: 2013-12-30 01:30:02 +0200

Seen: 136 times

Last updated: Dec 30 '13