ANDROID DEVELOPER + ANDROID MANAGER
JOB DESCRIPTION + DUTIES
It's basically easy stuff. You would maintain an Android Studio master file (for our E-Commerce App Solution/Template named “Pre-Order”) and then use the “master” to copy lots of new E-Commerce Apps - adding new images (ie. designs) for each, giving them their own App Name and publishing them in Google Play.
And, if there's an error you would try to find it, fix it or get a more advanced Android Developer to help you fix it, so we always keep a working master file. That's it.
BACKGROUND ON OUR WORK STRATEGY
Android is just a headache for me. I basically put all my focus on iOS, APIs and designs. So by the time I get the iOS perfect, then all we have to do is just make the Android App version just like it.
OUR APP UPDATING PROCESS
Usually, it's a matter of simply copying it and switching the name, bundle name and designs. Sometimes I add 1 new piece of info to a feature in the App, which means we have to modify an API call in the code and maybe add a new parameter to some existing set of parameters to be able to show some new info in the App for the Customer/User.
Note: I will usually show you a screenshot of our iOS code, where we modified or added to a feature, then you can find the similar code and area in the Android App to make a similar modification.
TROUBLESHOOTING ANDROID
This is an easy way to troubleshoot all my Android Apps:
-
All my apps allow Guests to checkout (you simply enter your First name, Last name, Email and Phone) just before the final Payment Options screen (where the User/Customer can pay with different options).
Then if you click the top blue "Pay With New Card" button, it loads a credit card form. IF it actually successfully loads the credit card form, then that is a very good thing! (Most likely everything works or will work perfectly). You don't have to actually enter a credit card to test (I’ll do that part). Just see if the form displays.
If it doesn't load that form, then there is usually a problem. (the form is webview based and provided by Square, the big payment company we use for all of our Clients). -
Secondly, we have an E-Wallet payment option. I'm modifying it (in the API) to make it simpler to use in the App(s). Then you'll be able to simply use a “demo” Customer/User Account on every app (ie the same email and password on every app) to quickly see if you can actually make a REAL purchase using the virtual E-Wallet funds that I load to the demo account.
That will REALLY let us know if things are working smoothly because I can see if the transaction went through successfully on the backend.
So, if both Step #1 and Step #2 are working then it’s usually a good sign that everything is working correctly on the Payment Options page, which is the final step in our Checkout process. Those are the BIG things for testing and keeping my apps smooth.