Ethan Marcotte's "Responsive Web Design" came out as a book in 2011, and with it the idea that one site should adapt to every screen instead of shipping a separate mobile version. Eziline adopted it quickly, because clients were tired of maintaining two sites. The same year the company crossed from a web design studio into custom web applications and CMS projects, the milestone we still mark on our about page.
One layout, every screen
Fluid grids, flexible images and media queries replaced the fixed 960-pixel canvas. Every new site in 2011 was designed mobile-first and tested on a drawer full of phones and the office iPad. It changed the design process too: Photoshop mock-ups gave way to style tiles and in-browser prototypes, because a static picture could not show how a layout would reflow.
Custom web apps and CMS projects
The bigger shift was in the kind of work. Clients who had started with a website now wanted the business behind it online: inventory, orders, customers, staff, reports. We built these as custom PHP applications with MySQL, role-based logins and dashboards, often alongside a WordPress site for the public pages. Several of those systems were the ancestors of the ERP, POS and hospital products that came later.
The technology stack matured with the work. Version control became mandatory on every project, staging servers became standard, and we introduced written specifications and milestone-based delivery so clients could see progress rather than wait for a big reveal.
Around the studio
- More developers joined than designers for the first time, reflecting the shift to applications.
- The support desk grew to handle hosting, updates and fixes for a client base that was now spread across Pakistan and abroad.
- Internship batches were larger, and the training material we wrote for them was the seed of the courses Ezitech runs today.
2011 is the year Eziline became a software house in practice as well as in name.
Looking ahead
With applications now the larger half of the business, the priorities for 2012 were about doing them consistently. Every project was using slightly different conventions, which made it hard to move developers between them and hard to support a system a year after launch. The answer was to standardise on a front-end framework for admin interfaces and a back-end framework for the PHP work, and to write down how a project moves from quote to delivery. We also wanted faster first releases: clients were happier when they could see and use something early, even if rough, than when they waited months for a polished whole. That instinct became the milestone-based delivery the company still uses. On the hiring side, the mix shifted further towards developers and testers, and the internship intake was planned to feed the team rather than run as a separate goodwill exercise.
