"Inspiration: My kid received his learner's permit. In Indiana, you're required to log 40 hours of day driving, and I believe 20 hours of night. All they give you is an official paper form for tracking this - the easiest thing to lose. I figured "Hey, I'm a developer!" So I used Xamarin, Azure Functions, and some free time to write a mobile app that tracks the hours. What it does: Tracks the hours in a super easy way. No thinking about it - just 15 minute increments, and a simple log. Automatically fills out the state form PDF so you don't have to. Automatically backs up to the cloud, in case you lose your phone. And you're never without the form when you're driving. How you/your team built it: Xamarin - Immediate Native Cross Platform Apps and they look great! Azure Functions - because it's simple log entries, the cost of keeping a web service around all the time was prohibitively high. It was also a good time to play with that functionality. SQL databases in Azure are cheap and backed up automatically - also good! Shared Code - Functions and Xamarin apps used the same models, so development time was only a day. The UX effort took a couple weeks as I tested it with friends. AppCenter - Tracking how users are using the app, so I can make it easier to use. No PII. Challenges you/your team ran into Backups without PII - Dealing with kids here. If they want to backup, I don't want to store personal information. So I followed I've seen in order numbers, where they're simple words, separated by dashes. I did that and auto-generated a PIN, too. That became their effective username and password. Easy to write down, or screenshot. And, not tracking teens. Accomplishments that you are/your team is proud of The auth system. Making it super easy to do something that's annoying but required otherwise. What you/your team learned: Azure Functions are great for scaling. Gradients in Xamarin layouts need to be a feature without a custom renderer or effect :) Might be a package to release there... Thinking about how young people use an app, and leaving out unimportant stuff, is hard. Friends will provide great feedback. Xamarin continues to be the [my?] fastest way to build a quality native mobile app. What's next for this project? Listening to the users and adding more capabilities if it makes sense. Adding support for more state forms as it expands. Possibly change the name to something more marketable/memorable :)"