I see what you're saying but it just doesn't fit my needs. 1) I think it's just as easy to modify and upload arduino code than to dig into the android api (for example) but the main reason is that 2) The hardware is a feature not a bug. So say I code some android app, ok great, now I got some lights. Do I let the screen timeout? Then I lose the power of at-a-glance notification. Better make sure it's always plugged in because I want the display on constantly. Ok, now I have to make a call, oops, I didn't put it back on the 'notification' app. And EVEN IF this was logistically ideal (it's not) high-rate polling of webserver traffic or network health, or weather, etc. with a smartphone app would be absolutely the worst way to do this sort of monitoring (if it's even possible)
I do see what you're saying, and a simple smartphone app may work for some people for some tasks, but not for what I want. I need it to be permanent, always-on, independent, stand-alone, at-a-glance, and perpetually attached to the computer. Every single one of these requirements are exactly opposite of what a smartphone app excels at.