You're neglecting the fact that Maemo5 is a very hostile environment for such apps. You have to fight your way around a lot of artificial restrictions the OS imposes on 3rd party apps (heck, there is even a hardcoded whitelist on the device of apps the OS trusts and doesn't impose restrictions on: the closed source Nokia apps that come preinstalled).
E.g. your app gets no sound in silent mode, there'll be audio stuttering when pushing the power button or locking the device, or the OS simply decides to give your app no CPU cycles, making it look jerky.
You're forced (!) to use the Maemo5 frameworks and APIs to get around that, and those usually perform poorly and don't have useful documentation, either. As if that was not enough poorly written background tasks kicked in for no apparent reason, taking even more CPU resources away from your application.
I fought all that way along and it was really frustrating at times. Add to that the non-existance of documentation when it comes to Maemo-internal stuff, and not getting much help from Nokia employees either.

Developing for Maemo4 and earlier was fun, but developing for Maemo5 was a struggle. Hopefully, it will become fun again with MeeGo.