How Methods Count Works


Libraries checked for the actual optimization process

Potential downloads before modifying the script

Uploads once the app is properly optimized

Breaking the optimization process down into small details

The core of Methods Count is easy to understand if you have a little experience. It involves fetching the library, extracting the jar archive and running dx to come up with the DEX file. Once all done, the Methods Count details are in the DEX header.

Find out more

Understanding the back end of Methods Count

There are a few different processes occurring while using Methods Count. The back end is split into two different parts – the user facing component and the actual background workers.

The back end of Methods Count was developed using Sinatra – a framework based on Ruby web development. The app is split into more services because different serving users come with different requirements in terms of resources, not to mention the library computation tasks.
As for the actual front end, the web application was simply developed using Javascript. The front end will grab a few APIs, which will occur during the back end stage. As for the design language, the app runs with Google's Material Design.

Methods Count has managed to achieve some impressive numbers so far – over 55,000 libraries and more than 16,000 of them are unique. Computed methods count over 71 million.

Definitely worth it

Understanding how Methods Count works will also help you figure whether or not it is worth the costs and expenses.

  • Profitability rate80%
  • Optimization rate60%
  • Protocols altered50%
  • Visible changes10%