Hmm... A big text on a UI.Card (on Pebble) crashes the watchapp.
I could design a string length handler and its own text display function...
Or I could divide the text into smaller chunks and call it a day.

Here we go,"4.5"! "4.5+"! "4.5++"!

And now I could look into why it crashes when pressing the back button on a semi long text...
Or I could think of it as an automated memory cleanup! Yeah, right! Awesome! Plus, it's only two press to go back where I was!