February 2nd, 2009
One of the big changes in web application development over the last year is its growth. No longer the domain of simple, little functions that serve a single purpose, web-based applications are now often part of larger, enterprise-wide development initiatives.
One of the challenges of being part of a bigger solution is the need to scale the development process. And in that, we’ve seen changes in two directions: moving towards the micro level with component libraries and moving towards the macro level with frameworks.
A few weeks ago, we published an article by Nathan Curtis on the differences between patterns and components. Nathan asserted (and we agree) that patterns describe cross-application behaviors, while components are the place within an application where the behaviors and the implementation meet.
Today, we’re taking a look in the other direction. Robert Hoekman talks about the differences between patterns and frameworks. He describes how a framework is a systemic view of a specific portion of the system. To contrast with Nathan’s components, frameworks are the place where behaviors meet enterprise-wide thinking.
If you’re involved in making web-based applications a key development platform, then you’ll want to understand how frameworks will make large-scale projects that much easier. Today’s article, Web Anatomy: Introducing Interaction Design Frameworks, is a good introduction as to why that is.
Of course, this is just the tip of the iceberg. If you want to know more about frameworks, you’ll want to attend Robert’s full-day seminar, Web App Anatomy: Effective Interaction Design with Frameworks, at the UIE Web App Summit in April. And you’ll love combining it with Nathan Curtis’s seminar on patterns and components. More details on both at http://webappsummit.com
Have you started to put together frameworks? Is this something you’re exploring? Share your thoughts and comments below.Tweet