Austin 
Time for another late night update on #LAHistoricalMarkers. I’ve put the finishing touches on full screen photo viewing (with support for screen rotation) and am working on TestFlight/Play Beta builds now!
Multiple photo support is coming along nicely in #LAHistoricalMarkers!
I still need to create an interaction for full screen viewing (including handling of orientation). And then it’ll be time for another Android UI pass… 😅
Lots of work left to do, but I’m really excited about improving the experience of adding photos in #LAHistoricalMarkers! It turns out, #expo supports Apple’s Live Text Interactions, which means users on iOS could extract text from photos that they could use in their submissions!
#LAHistoricalMarkers is once again available on the #GooglePlayStore! It looks like the version that is up now is fairly behind, so I'll be working on getting that updated as soon as possible.
If there's any interest, I'd love to have some help testing the app on Android. One of my focuses for this next release is a UI/UX pass specifically targeting Android.
https://play.google.com/store/apps/details?id=com.austinwebre.lahistoricalmarkers
Alright, time to see if this will appease the powers that be over at Google. Since I had to add a whole page just to link out to our new Privacy Policy, I decided to add a feedback form and make some general improvements. Not bad for a night’s work!
Backend changes are deployed, Android build is in progress and the iOS build is queued up right behind it.
Since Google Play is insisting that my Privacy Policy be accessible from within the #LAHistoricalMarkers app itself, I decided it was time to put up an actual website for the project.
Introducing to the world for the very first time:
https://lahistoricalmarkers.com
#WebComponents + #elevent + #GitHubPages made this a pretty quick project, all things considered!
I have officially entered the upside down. My latest changes to #LAHistoricalMarkers are up on TestFlight and staged to go to Apple Review, but Google Play has taken down our entry on the App Store and is refusing to allow updates until I jump through some hoops.
Going to be a fun time getting this thing cleared through their review process.
It is complete. Both the web API and queue processors for #LAHistoricalMarkers have been moved from #AzureFunctions over to #AzureContainerApps!
Next up is probably attempting to automate my #Expo build with #EAS.
Check out the code on #github!
GitHub - awebre/la-historical-markers: LA Historical Markers is an iOS and Android app for exploring Louisiana's Historical Markers. The mobile app is built in Expo and the back-end is a combination of Azure Functions, MSSQL, and Azure Storage.
LA Historical Markers is an iOS and Android app for exploring Louisiana's Historical Markers. The mobile app is built in Expo and the back-end is a combination of Azure Functions, MSSQL, and Az...
Still more functions to migrate over, but I got a little distracted with setting up the domain for the new #LAHistoricalMarkers api. So not only is it live, but you can view/interact with it via #Swagger at https://api.lahistoricalmarkers.com
#AzureContainerApps require manual cert uploads for setting up a custom domain, which I thought was going to be a deal-breaker. Enter the #OpenSource community with an #AzureFunction that automates #LetsEncrypt with #AzureDNSZones. Maybe this should be a blog post?
An hour or so later, the baby is fed and fast asleep and I have fully automated deployments of the new backend. It was the Auth between GitHub Actions and Azure that tripped me up.
#AzureAD and BRAC are things I don’t touch very often in the day job. All our connections between services and azure were configured long ago.
So far this has been smoother than I could have hoped. I’m actually getting excited for the prospect of a #LAHistoricalMarkers mobile app release!