[gregsadetsky]

What position are you interviewing for?

If it's heavier on the engineer side, letting the number of downloads speak for itself (as an indicator of your apps' success and indirectly of your quality as an app developer) could be enough.

If interviewing for a PM / management position, revenue could be a useful indicator that you managed both the development and some aspects of marketing / bizdev. It might also be interesting to break down revenue per month/year, if you want to show growth patterns. This is something that could become a good talking point during the interview ("I've learned that my apps do better in X markets during Y times of the year, which is super interesting because...")

Also depends on the company (big? small? nonprofit? etc.), what they value (their "culture"), etc.

(Congrats on your apps' success by the way) :-)

[caspercrf]

It would be for a senior QA/test/automation engineer position. I don't have an impressive GitHub account and I wanted to show that I have an interest in writing code outside of work.