Last year, when I was brushing up on some of my web development skills, I wrote:
At the time I was working on a now abandoned/delayed project where I chose not to use any frameworks. It was invigorating, to an extent, but also overwhelming, because every single pixel needed to be styled.
When we conjured up the idea for Notify My Team, things were different. Time was of the essence because we didn’t know what the future held for Detailed Image and e-commerce in general. I needed to develop rapidly, at least at the start during the most uncertain times, and the best way to do that is with a framework. I’m also not a designer by nature. I enjoy UI/UX, but am better working within a framework and not completely on my own.
I chose Materialize, which I think is a nice sweet spot between larger, more bloated and complex frameworks, and super simple frameworks. It checked all of the boxes for what we needed, and as we approach our launch day, I’m still quite happy with the decision. In a future post, I’d like to break down what frameworks I would use in what situations, because I think this is a fascinating topic. The decision you make when you start a project can have long term benefits, long term consequences, or (in most cases) both.
- How Twitter, WordPress, and Google Contacts Influenced Notify My Team’s UI
- When Skills Accidentally Get Stuck in Time
- The Inside Scoop Behind The New SportsLizard
- HTML5 or Native Apps? Why We Chose HTML5 for LockerPulse. Plus – Our Awesome New Shirts
- On the LockerPulse Blog: Making HTML5 and Responsive Design Work for Web Apps Like LockerPulse