… or you can just close your eyes, and move your face around. The device will not unlock if you're not looking at it and after 3 or 4 tries will ask for the password.
I remember writing apps for PalmOS (long time ago) distributors like PalmGear took over 60% from international developers like me, plus they held your earnings until you hit a minimum payout threshold. Add bank fees on top of that, and it was basically not worth developing for the platform. 30% felt like a godsend in comparison. (I'm not defending the Apple / Google tax)
This kind of thinking is exactly why Electron-based apps end up consuming 4% CPU while doing nothing, and why some games use 100% CPU just sitting in their menus.
Why would you expect users to manage threads, processors, and system resources themselves?
I hope this helps people to consider Swift 6 as a viable option for server-side development, since it offers many of the modern safety features of Rust, including simpler memory management through ARC, compared to Rust’s more complex ownership system and more predictable than Go's garbage collector.
Custom controls are the enshittification of the <video> tag. IMHO there's no custom video component that allows the user to control volume, picture-in-picture, AirPlay, control speed and scrubbing better than the standard controls, especially on mobile.