It’s all one piece, the elongated neck was before breaking the pulled part off and opening up the lip

Worst case, they do a bunch of deeply incredibly unpopular things with their base

and obviously why not call their bluff?

I would maybe loosen that guidance to primarily just avoid escaping values out of a GeometryReader update closure

Try adding a .geometryGroup() around the whole body of the card so it all slides together in one layer

Currently on a plane post update, seems to be okay!

For sure if I intended for this to be a proper service with many accounts and such, and I felt like I was going to need to run many migrations over time without just blowing out the database and creating a new one, I would have picked Vapor and Fluent and probably used Postgres instead

Mainly seemed like it was a smaller surface -- I didn't want to bring in the whole fluent stack for a tiny service. SQLite.swift is gonna be all I'll ever need for this side project.

I don't think 69ºC counts as "nice" weather!

I'll put the app on TestFlight soon. You can sign up as long as you're okay with me having your location 😬. I also of course have account deletion that fully wipes everything associated with you.

Mainly an exercise to brush up on server-side Swift and make sure I can still do things like make an authentication system and deploy an SSL-protected server at home. I also vibe coded a simple web app and web push support so my roommate can use it.