There is a major programme of developments lined up for Affino in 2012. This post outlines many of the key ones. Whereas 2011 was something of a transitional year for Affino (although we made some great headway see here and here). 2012 will see many key milestones reached which will open up Affino to provide great sites on all devices for great commercial and community based sites.
For an indepth look have a look at the Mindmap here. For a quicker overview see below.
- Adaptive Design
- HTML 5
- Usability and Learnability
- Affino 7
You can see more details on each of the key priorities below.
We will also maintain attention to:
- Overall Product Quality
In 2011 there were over 1,400 Affino development projects and there’s no reason to think there will be fewer this year. Which means that there will be a lot more that’s not on this list.
Note that as always priorities are open to change, however all elements outlined are firmly on the Affino roadmap and will be rolled out at some point in 2012.
Affino’s approach to Mobiles and Tablets is Adaptive Design, as opposed to Responsive Design. Responsive Design repurposes existing assets for different design factors and can be very slow on mobile, especially for media, it also so doesn’t optimize user interfaces as far as they could be.
Adaptive Design means tailored interfaces for mobile and tablets, optimized for different form factors and OSs. This means that we’ll be tailoring the way different elements in Affino work on different form factors, and whilst you will need to put thought into how you lay out your mobile sites in particular, much of what Affino does will be to handle the transition between devices gracefully.
We’ll also be rolling out a Mobile App API which initially will support iOS and Android.
HTML 5 is a term which actually covers a lot of developments which are aimed at providing native browser capabilities to replace many plugins, in particular to replace Flash. We started replacing Flash elements in Affino over a year ago and the goal this year is to replace all remaining Flash / Flex elements with native browser elements. We won’t just be replacing them, we’ll be...