I know you guys sometimes get frustrated at the crashes in Sweeter Home, and although I’ve covered this in several forums I thought I’d mention it here as well (with a nice example).
Sweeter Home isn’t a ‘normal’ home replacement app. In a ‘normal’ home replacement you are working within a set UI paradigm; working within the framework of that home app. No matter how flexible and customisable it is, NO home apps allow you to completely add, remove, or replace elements of their UI, let alone doing this on-the-fly. So Sweeter Home is unique in this, but in doing so it also opens some doors to functionality that Android is not optimised to perform. A good example is bitmaps. Read this article to see an example where using bitmaps in a gallery app just to find image widths was crashing his app, and his solution was to avoid using bitmaps! This is problem with how Android allocates memory for bitmaps and all apps have to deal with this. Now imagine adding more bitmaps, a completely editable UI, the half-baked Android widget framework and multiple devices all with varying processing power and RAM, and you’ll have some idea of what the developers of Sweeter Home have to work with when trying to get the app running smoothly on your phone.
Remember the app is in beta, and the developers are working on getting more resources to start expanding functionality. Until then have fun with Sweeter Home and be patient! 
Oh, and share your themes!
(PS – Theme tutorial is coming soon)…
