Amanda Roos

I receive a lot of reviews of scorekeeper asking for the ability to edit the names of players, which is a feature already available through long-pressing on the player name. Apparently, long-pressing is not something intuitive to try for some people, so they are left without the ability to change the player name. I hope this video preview helps make it easier for users to understand how the app works and how to get to additional features already available to them.

This is my first published app built with Kotlin! :) Features: Use volume buttons to keep score for two teams Can reset to any scores you choose Available in 100 languages Code on GitHub .

The code from this video is on GitHub if you want to copy and paste: https://github.com/amandafarrell/LatLong This video is based on the android dev page for getting last location: https://developer.android.com/training/location/retrieve-current

This app got 25 downloads and a five-star review in its first week on the Google Play Store! Code on GitHub

I made a python tool (which uses selenium and chromedriver) that takes in a phrase to translate and an array of language codes of the languages you want to translate the phrase into. It creates google translate URLs, copies the translations into an array, and then prints the array (which I then use to copy into Android Studio's translation tool). Here's a link to the python code for anyone interested:  https://github.com/amandafarrell/PythonTranslationsTool/blob/master/Translations.py Most of my app downloads are not in English (for example, my Scorekeeper app has been downloaded over 20,000 times and less than half of those downloads are in English), so it was worth it to me to manually create translated versions of my apps, but going forward I wanted to do less copying/pasting. Hopefully, this tool is helpful to others as well!

My Scorekeeper download stats show a consistent spike every Saturday, and big spikes around Christmas and New Year's. I wouldn't have predicted it, but it totally makes sense that people would play more games on weekends and holidays. 

A quick overview of uploading to the Google Play Store. This is as of December 2018. Some things have changed since I uploaded my first app in July 2017, but overall the process is still very similar.  Even though things will probably change a bit if you are watching this months in the future, I thought it would be worth it to make a quick video. App code on GitHub .

Code on GitHub.

See the app code on GitHub.

1. The first part is setting up your Android phone to get developer options. You can use the Android Studio emulator, but it's much faster to use a physical device. Go to Settings > About phone > tap Build number 7 times. Once you have developer options make sure that USB Debugging is turned on: 2. Next, download Android Studio:  https://developer.android.com/studio/ 3. Start a new project. There are template projects available or you can start with an empty project: 4. Switch to Project view: 5. Java files go in "java" folder, XML files (layout, styles, strings, etc.) go in the "res" file, and sometimes you edit the manifest and the Gradle files: After this, be prepared for downloading time as you might need to update Android Studio. If you want more help with a starter app, check out my counter app tutorial video:

Thanks to Google and Udacity for the scholarship, and thanks to everyone else I got help from along the way. I've been lucky to have so many people willing to take time to answer my programming/Android questions.

See the app code on GitHub.

Link to video:  https://youtu.be/fouAGhpq8Ss This simple app displays the latitude and longitude coordinates of the phone using Google's location services API and the getLastLocation() function as of June 2018. The code is on GitHub: https://github.com/bluepandadev/Location2 I was following along with Udacity's location class when I came across a deprecated method. Since Udacity doesn't have an updated video for it yet, I decided I'd try making one.  Let me know if you have any suggestions on how to do this better. Link to the Udacity class, Google Location Services on Android: https://www.udacity.com/course/google-location-services-on-android--ud876-1 Here's a training doc on location from the google dev website: https://developer.android.com/training/location/ And here's the Google APIs for Android, LocationServices page on the google developer website for more information: https://developers.google.com/android/reference/com/google/android/gms/loc

See the app code on GitHub

This video shows how I put the finishing touches on my Change Calculator Android app (which will be on Google Play for download soon!). Example of using string.xml, style.xml and color.xml files in an Android app.   Websites from the video: https://www.materialpalette.com/ https://stackoverflow.com/ Link to Change Calculator code: https://github.com/bluepandadev/ChangeCalculator Edit: link to the app on Google Play -  https://play.google.com/store/apps/details?id=com.amandfarrell.www.changecalculator&hl=en

Scorekeeper for Android is done with beta testing and available on Google Play! Check it out:  https://play.google.com/store/apps/details?id=com.amandafarrell.www.scorekeeper&hl=en#details-reviews The code is also on GitHub:   https://github.com/bluepandadev/Scorekeeper

This is a quick tour of how the SQLite database in my simple scorekeeper app is set up. Here's a link to my scorekeeper app code on GitHub if you want to follow along: https://github.com/bluepandadev/Scorekeeper If you want more information on Data Storage and Android, check out this class at Udacity: https://www.udacity.com/course/android-basics-data-storage--ud845 The scorekeeper app is on the play store (in beta still right now): https://play.google.com/store/apps/details?id=com.amandafarrell.www.scorekeeper&hl=en A link to the screen recording software I used:  https://obsproject.com/

This is a 3-minutes video about how to make a simple counter app in Android Studio. I recommend using your own Android phone if you want to try it out, though you can also use the emulators that come with Android Studio if you don't mind waiting patiently while they load.