@boomzilla You're making a mistake that a lot of inexperienced software engineers make - tightly coupling the data model to the user interface. When developing your data model, you should never ask how something will be presented to the user. The data model should only be designed to store the data for your system as completely, accurately, and consistently as possible. If you get something wrong in the design of your data model, it can be a major project to fix it, since it potentially affects every part of the system that depends on it. Making changes to the presentation layer, on the other hand, is generally pretty straightforward, since nothing else depends on it.
This is why the MVC paradigm easily became so popular. It's what any competent software engineer, who learned about separation of concerns back in school, would naturally do.