Making IDAGIO
Last year saw the launch of both IDAGIO.com and IDAGIO for iOS. Today, our team consists of 21 people with various skill-sets from all over the world.
The engineers and designers working at IDAGIO are divided into teams working on three main areas of development:
- Backend, APIs and Infrastructure
- Web Application
- iOS Application
On each team there’s a product manager and a technical lead. Each team has the freedom to use any technologies they choose for their part of the stack. JavaScript, Ruby, and Swift are our primary programming languages, however, with everything we build, we have the choice to use something different when it makes sense.
For the Web Application, we knew early on that we had to provide a single page application, we also knew that we wanted it to render both server-side and client-side for performance and SEO reasons. We decided to use a stack featuring Node.js, React, and Redux. We began development in August 2015, and launched the first public beta in November 2015.
Our iOS application was originally written Objective-C. We’ve been migrating the codebase to Swift, as we’ve implemented new features and made changes to our API. For the management of swift libraries, we use Carthage.
On the API and Backend side of things, originally we were powered by a monolithic Java™ Spring application. In late November 2015, we decided to migrate away from our monolith, to a more service oriented architecture. This move was primarily driven by the fact that development time on the monolith was slow and fraught with issues. We now service all API Requests with Hapi.js, which proxies our old API whilst we move away from it.
We use Fastly as our primary CDN, however, we’re not using their on-the-fly transcoding, instead we do transcoding of our repertoire ahead of time.
In this publication, we’ll be sharing articles about the things we’ve learnt making IDAGIO, and code we’re open-sourcing as a byproduct. Subscribe to this publication to hear more from our team in the future.
(Apologies, we’re currently not available in the U.S. and Canada, click here to get notified of when we launch in your region.)
