Thanks! It looks good - it's nice having the global drawContent function to handle all different notifications.

Just because we're on a device without too many resources (and gadgetbridge is running in the background with other apps in the foreground), there are a few things that I'm not sure are a good idea...

Basically, on Bangle.js function code is stored and executed from Flash memory, so doesn't use any RAM. Stuff that does use RAM is any variables/objects (even const) and each function declaration (just not the code in it).

• Stuff like musicState.STOP is defined and used once. It makes it harder to see what the code is actually checking against, but it's using extra RAM in order to store the whole musicState structure. I guess if we moved to minification then the minifier would undo that for us though.
• I wonder about making the images external vs. inline, especially for small ones? I know it does make code a little more readable, but where it's only ~100 bytes of code I'm not sure if it's really that much of a win, as having to search for and load another file first slows things down

There's another PR (#130) for handling fullscreen notifications which abstracts stuff in a similar way, and I think perhaps this would be a good time to actually split Gadgetbridge up - having the main gadgetbridge handling just the decoding, with another (choosable) app handling how those notifications are displayed.

I'll leave this and the other PR open until I get a moment to merge both

Specifically: #162

Thanks for your time!
I wasn't aware that the variable declarations are affecting the RAM usage so much. I will look into this in the next days.

I inlined the variables again and restored most of the notification code. That should make it easier to integrate it with the other PRs.

Thanks for this! Just merged.