@gennarodp
Don't change the tabindex on your controls! Your tab stops should be based on the order of the controls on your screen. If you need specific ordering, use a control group. The documentation has a stern warning on changing the tabindex based on the W3C warning of the same.
Now, given that, the tabindex does not seem to be the concern in your post as you are stating you want it to go to the password control immediately after the username is filled in.
So, my question would be this - how would you know that the user has filled in the username? Do you have some sort of fixed length usernames? Do you have some sort of validation list with usernames in it?
I see problems with this as (unless there is some pattern to your usernames), if you have a BillHarris and a BillHarrison (for example), how would your app know that BillHarris was entering their username and were "done" to go to the password control versus BillHarrison is actually trying to enter their username?
Also - consider your approach to needing someone to "log in". In order for them to run the App, they already have needed to login. Your app can get the information about that login as needed (i.e. username, etc.)
The only real situation where a "login" would be needed is where the app is running as a single device shared app such as a kiosk or entry point.
I hope this is helpful for you.