Optional Features
NOTE: Any feature you implement that is, in the opinion of the staff, added solely for the purpose of earning
points and do not make sense in the context of the app will not receive full points, if any.
7 pts - GPS / Location-awareness (includes using Google or Apple Maps)
- Your app uses the location of the user in some meaningful way in the app. A plain Google Map with just
your location and no modification will not earn full credit. (7: Excellent, 5: Good, 3: Reasonable, 1: Poor, 0:
Does not work)
7 pts - Camera
- Your app uses the camera to take a picture and use it directly in the app. The image is saved somehow,
either locally or remotely. (7: Excellent, 5: Good, 3: Reasonable, 1: Poor, 0: Does not work)
5 pts - Device Shake
- Your app responds in an appropriate way to a device shake. "Made up" usages that don't make sense will
not earn many points. (5: Excellent, 4: Good, 3: Reasonable, 1: Poor, 0: Does not work)
7 pts - Accelerometer
- Your app responds in an appropriate way to tilt movements. (7: Excellent, 5: Good, 3: Reasonable, 1: Poor,
0: Does not work)
7 pts - Microphone / Audio management
- Your app uses the microphone to record audio and/or has advanced audio playback capability. Simply
playing sounds when a button is pressed does not count for this feature. The feature must make sense in the
context of the app (i.e. a random music player bolted onto something is not sufficient). (7: Excellent, 5: Good,
3: Reasonable, 1: Poor, 0: Does not work)
10 pts - Build and consume your own web service (including all server-side code)
- Your app uses a web service that you built yourself from the ground up. This service may running PHP,
Python, or some other appropriate language and hosted on approved server. (10: Excellent, 8: Good, 6:
Reasonable, 4: Has issues, 2: Poor, 0: Does not work)
7 pts - Build and consume your own web service using a third-party platform (i.e Firebase)
- Your app uses a web service that requires some level of serious customization. A good example is Firebase,
a mobile-ready cloud-based database you can use for free. A login feature that uses Firebase counts for this
rubric item. (7: Excellent, 5: Good, 3: Reasonable, 1: Poor, 0: Does not work)
5 pts - Consume a pre-built web service
- Your app consumes some readily-available data source, such as weather or stock prices. This feature must
make sense in the context of the app (i.e. randomly loading the weather in an app that doesn't need is not
sufficient). (5: Excellent, 4: Good, 3: Reasonable, 1: Poor, 0: Does not work)
10 pts - Data storage using SQLite (Android)
- Your app stores data locally in a relational-type database model. (10: Excellent, 8: Good, 6: Reasonable, 4:
Has issues, 2: Poor, 0: Does not work)
7 pts - Data storage using file read/write or data serialization read/write
- Your app stores data by either taking data structures (Array or ArrayList) and serializing them for direct
writing to disk or you have your own data format you write to disk. (7: Excellent, 5: Good, 3: Reasonable, 1:
Poor, 0: Does not work)
5 pts - Data storage using key/value pair storage (SharedPreferences or UserDefaults)
- Your app stores data in the provided key/value storage system of your platform. (5: Excellent, 4: Good, 3:
Reasonable, 1: Poor, 0: Does not work)
5 pts - Open shared activity / features (i.e. Create an email to send, share with a text message, etc.)
- Your app interacts with another activity or feature of the device by passing data in a reasonable way. (5:
Excellent, 4: Good, 3: Reasonable, 1: Poor, 0: Does not work)
Complete at least 30 pts for full credit. Points do not have to add up exactly to 30, but no more than 30
points can be earned.