QUOTE(apache_utara @ Jul 21 2014, 01:13 PM)
I'm using it with my Nexus.
I don't it is warez as the author himself ranted in his website about twitter phasing out 3rd party twitter apps in favor of their own, hence the limited token.
Since the app is already endorsed by the author, and i never read any article from twitter prohibiting such actions (if any then I apologize), so i guess its okay to share here

Ok then, I tried to improvise from this
guideOn your device or computer:
1. Visit
https://dev.twitter.com and sign in (it doesn't matter what account you use for this step)
2. Click on "Create new app"
3. Fill in a unique name (you may have to try a few names before you get one that hasn't been claimed), a description, and URLs for the Website and Callback. It doesn't matter what URL you are using, but it must be correctly formed (http://something.com).
3. Check the box to agree to the "Developer Rules Of The Road", and click the button to finish.
4. Click on the "Permission" tab and change the Application Type to "Read, Write and Access direct messages," then click the Update button at the bottom of the page.
5. Switch back to the "Details" tab, go to "Manage API Keys" and copy the values for "API Key" and "API secret."
In Falcon Pro:
1. Go to the login screen (logout if you're logged in)
2. Tap all four corners to light up the squares , then tap the orange one (bottom left) to turn it back off.
3. Shake your phone/tablet. Yes, really, start shaking it until a dialog box pops up saying "Custom login unlocked!"
4. Tap on "Custom login"
5. Fill in "Consumer Key" and "Consumer Secret" with the values you got from creating your Twitter API key. These are long, case-sensitive strings, so be careful to copy them precisely.
6. Then you can login and use Falcon Pro now.
Needless to say, Twitter probably won't be happy about this turn of events. Fortunately for us, there isn't a lot the company can do without shutting down API access for all 3rd party clients or restricting new API keys. As more clients reach the dreaded token limit, this approach will probably become increasingly common. Hopefully, the powers that be will overlook this loophole or reconsider the policy all together.