Closed GoogleCodeExporter closed 9 years ago
I don't think that a splash screen makes sense here. Generally splash screens
are a bad decision on Android and one should consider using them very very
carefully. There are only very few cases where a splash screen makes sense
(games, apps with heavy background work on startup).
Since HABDroid has no heavy lifting to do a splash screen would probably be
more harmful. HABDroid and other applications like it should be designed to be
fast accessible. Delaying the start of the app unnecessary long would work
against a fast and easy accesibility.
Ultimately it is Victors choice if he wants a splash screen, but I would advise
against it, except all the sitemap loading and parsing is moved to a background
service enabling you to do work on the splachscreen.
Original comment by till.klo...@gmail.com
on 24 Jun 2013 at 10:43
I fully agree but eye-candy sometimes matters too.
Moving connection and initial parsing to a splash screen should be step two and
absolutely makes sense.
Nevertheless, I hope to find this feature in the long-run. Thanks for your
comment!
Original comment by hlw31...@gmail.com
on 24 Jun 2013 at 10:53
I would tend to agree with Till here - HABDroid is usually very fast in startup
and a splash screen would be rather disturbing. Also, checking my Android apps,
hardly any of them uses a splash screen, so this does not seem to be a
"standard" feature. Especially as you usually want to do something quickly when
starting HABDroid, every additional waiting time is annoying.
@Victor: I assign it to you to take the final decision on this request :-)
Original comment by kai.openhab
on 24 Jun 2013 at 11:36
I continuously analyse HABDroid usage patterns and a typical pattern is 1-2
sitemap pages with session lenght of less then 1 minute. So I continuously work
on minimising HABDroid startup time for all use cases, so I would reject this
request. Sorry. For 99.99% of users this will make experience worser ...
Original comment by belovic...@gmail.com
on 22 Jul 2013 at 6:36
Original issue reported on code.google.com by
hlw31...@gmail.com
on 24 Jun 2013 at 10:11