Latest blog entries

Erlang and Elixir Factory Lite B.A.

A brief introduction about what was the Erlang Factory Conference in Buenos Aires for some Inaka team members

Jul 07 2017 : Euen Lopez

The Art of Writing a Blogpost

The Art of Writing a Blogpost

Apr 11 2017 : Matias Vera

SpellingCI: No more spelling mistakes in your markdown flies!

Feb 14 2017 : Felipe Ripoll

Fast reverse geocoding with offline-geocoder

Do you need a blazing fast reverse geocoder? Enter offline-geocoder!

Jan 18 2017 : Roberto Romero

Using Jayme to connect to the new MongooseIM REST services

MongooseIM has RESTful services!! Here I show how you can use them in an iOS application.

Dec 13 2016 : Sergio Abraham

20 Questions, or Maybe a Few More

20 Questions, or Maybe a Few More

Nov 16 2016 : Stephanie Goldner

The Power of Meeting People

Because conferences and meetups are not just about the technical stuff.

Nov 01 2016 : Pablo Villar

Finding the right partner for your app build

Sharing some light on how it is to partner with us.

Oct 27 2016 : Inaka

Just Play my Sound

How to easily play a sound in Android

Oct 25 2016 : Giaquinta Emiliano

Opening our Guidelines to the World

We're publishing our work guidelines for the world to see.

Oct 13 2016 : Brujo Benavides

Using NIFs: the easy way

Using niffy to simplify working with NIFs on Erlang

Oct 05 2016 : Hernan Rivas Acosta

Function Naming In Swift 3

How to write clear function signatures, yet expressive, while following Swift 3 API design guidelines.

Sep 16 2016 : Pablo Villar

Jenkins automated tests for Rails

How to automatically trigger rails tests with a Jenkins job

Sep 14 2016 : Demian Sciessere

Erlang REST Server Stack

A description of our usual stack for building REST servers in Erlang

Sep 06 2016 : Brujo Benavides

Replacing JSON when talking to Erlang

Using Erlang's External Term Format

Aug 17 2016 : Hernan Rivas Acosta

Gadget + Lewis = Android Lint CI

Integrating our Android linter with Github's pull requests

Aug 04 2016 : Fernando Ramirez and Euen Lopez

Passwordless login with phoenix

Introducing how to implement passwordless login with phoenix framework

Jul 27 2016 : Thiago Borges

Beam Olympics

Our newest game to test your Beam Skills

Jul 14 2016 : Brujo Benavides


Three Open Source Projects, one App

Jun 28 2016 : Andrés Gerace


Running credo checks for elixir code on your github pull requests

Jun 16 2016 : Alejandro Mataloni

See all Inaka's blog posts >>

Gadget + Lewis = Android Lint CI

Fernando Ramirez and Euen Lopez wrote this on August 04, 2016 under android, ci, gadget, github, gradle, java, lewis, lint, xml .


As Android developers, we don't want to merge whatever code we write to master, that's why we should use pull requests. But, being honest, we don't want every time we have a pull request to spend so much time with it either.

Our goal was to review pull requests easier, faster and better.

So, Android developers, here we are to present the tool that is going to change the way you review your pull requests. Be ready to meet... Lewis!

We included our customized Android linter, Lewis, in Gadget.

Don't you know Lewis?

Lewis is an extension of Android Lint that adds some new rules that follow our Android guidelines.

Some time ago, we made a blog post introducing it.

What is Gadget?

Gadget is a service with associated tools for different languages. You can enable or disable them in order to allow or disallow this tool to analyze the code in your pull requests.

Nowadays, Gadget has the following tools:

  • compiler (erlang)
  • xref (erlang)
  • dialyzer (erlang)
  • elvis (erlang)
  • lewis (android)

How to use it

1. Open Gadget

If you want to integrate Gadget with your Github repo, go to and follow the steps.

2. Turn on Lewis

If you turn on the lewis tool in your android project Github's repo, the code in your pull requests will be sent to Gadget when they are created or modified.

3. Allow comments

Add this to your app/build.gradle file:

android {
    lintOptions {
        abortOnError false

Gadget will analyze the code according to Lewis' rules and it will insert comments if errors or warnings are found.


To see an entire example of a pull request using Lewis, click here.

Scope and clarifications

Gadget as a free service tool will only work on public Github repos. Additionally, with the free modality we can't guarantee that at some point it won't go down for a couple of hours.

Considering the two items above, if you want Gadget for private repos we can help you to build a server with that for a reasonable price.

For more information, please contact us.



For questions or general comments regarding the use of this tool, please use our public hipchat room.