So you have a nice application that has to run all the time (because it detects a sensor, it reacts on something, whatever)... People love it and want to use it.
Then you have stupid WM limits. You can have only 32 processes mister (and 32MB for them)... Yeap that's all for you, even today and WM 6.5 (expected to change with WM7 but WM7 if it ever comes, is at least 18 months away)...
Then you have modern devices that from the factory come loaded with things you want to use and these 32 processes are already half "eaten"...
Then us geeky users, try to add more things and before you know it: "Cannot execute whatever.exe" (inc. even your sync subsystem... no discriminations here)... Then some of those nice programs those nice people in XDA devs made... have to go.
Microsoft HAS an workaround though. A workaround that is used in your desktop windows much more, even though desktop windows don't have this stupid limit: SERVICES.
It's even a philosophy thing: Something that has to run all the time, should be service! Something that you don't want the system to kill it for you, should be service! Something that runs in the background "invisible" SHOULD be service!
Here are some nice links for you:
Yes a service is a bit more complex thing to build and handle (for example you cannot just "quit" a service), but the results are there; and after all this is what some apps SHOULD be.
...So I am making this thread to have a nice AND ESP. FRUITFUL discussion about shifting your great creations to services (i.e. to whatever app this applies). The issue is there. The solution is there. Don't turn a blind eye to it.
(ps. I'd love if someone makes this sticky eventually)