Frontjet

The Yerevan, Armenia studio Frontjet designs interfaces and writes front-end code for websites, web applications and mobile apps. The team works on UI and UX design and front-end development, with a focus on high-quality websites, responsive web interfaces and mobile applications. The work runs from research and wireframes through to finished, hand-coded pages, and the team works in agile sprints with its clients.

Prototypes and wireframes before any code is written

Every project starts with the client's needs. The team gathers those needs, follows current web design trends, and prepares prototypes and layouts that set out the user experience before anything is built. Its sketching, prototyping and design refinement stage covers research, definition, brainstorming, planning, analysis and the design itself. The studio says each phase should end with a clear conclusion that guides the next one.

Clean front ends built on Bootstrap 3

Frontjet builds rich interfaces mainly on the Bootstrap 3 mobile-first framework. It says it works with the latest web technologies and writes clean, semantic code by hand rather than relying on generated markup. The toolset includes HTML5, CSS3, LESS and SASS, along with JavaScript. Its stated aim is to turn mockups and wireframes into designs with a polished look, and it describes its finished work as pixel-precise.

Web applications on AngularJS, ReactJS and MeteorJS

Where a client needs functional web applications rather than static pages, the team builds them on AngularJS and ReactJS, and it also uses MeteorJS. The studio has experience designing and building native iOS and Android applications, combining an intuitive interface with backend functionality that performs well under load. Its service covers the design, the front end and the logic that connects them.

Working in sprints from backlog to retrospective

Projects follow an agile rhythm. The team grooms the backlog, plans each sprint, reviews the finished increment with the client and then holds a retrospective to decide what to change next time. This keeps scope visible and lets a client see working results at regular intervals rather than waiting for a single handover at the end of a long build.