This bill is a strictly better version of the age gating initiatives that have been passed in other states and countries like the UK and Australia. If age gating is inevitable, and it seems as though it is, this is the least bad way to do it — enforcing the onus on device manufacturers, who can do verification one time and then throw away the information.
It would easily mean that you're required to have an unmodified device, running a locked down system, to be able to access any service that uses age verification.
Although, a much more sensible alternative, would be to have parents (that do want the control) give their sons devices that send the "minor alert" signal, and have the services detect that.
Claude has an order of magnitude fewer users on its web product while training models that are just as large and advanced as OpenAI, so this makes sense.
Seems like a cool concept! I downloaded and entered an email address but haven't received a verification code yet after 10 minutes. It's an Apple Private Relay email if that matters.
Also, side note: magic link or email-based OTP login is by far my least favorite method of login, especially for a phone app. It's cumbersome, annoying, and completely unnecessary now that passkeys exist. Barring that I'd still rather use email/pw login any day of the week.
That's weird, can you try hitting back and then the forward arrow again? That should resend the email. If that still doesn't work, let me know and we can investigate on the backend.
We've definitely been hearing from users who don't like OTP, we'll try to get additional login options added soon.
I eventually had it come in another few minutes after I left the comment. And sounds good! I’ve had good success with Clerk for auth in the past.
Now that I’ve gotten to play around with the app I have to say I’m impressed with how smooth it feels and how well the Swift interpreter works (at least on the basic prompts I’ve tried). One suggestion: allow toggling between an “edit” mode and a “view” mode. The latter would full screen the app and hide the interface for follow up prompts, etc. that would make it easier to approximate how the app will behave in the wild.
I could see this eventually turning into sort of a social platform for mini-apps, by the way! Where users don’t even necessarily need to publish to the App Store if they’re just creating something for themselves and a few friends.
We probably need to make this more discoverable, but if you keep swiping down on the prompt area, you can swipe it completely off screen and your app will be full screen (with a small movable floating button to exit).
I really like the idea of a platform for people sharing mini-apps! It would be great if people could make lightweight specialized apps for different niches and share them with less friction.
That’s interesting, on a desktop device I would agree. However having to create an account on 1Password for an app I just want to try is a pain compared to using Apple’s Hide my email and entering in the OTP. I get that it didn’t work for you but it did for me.
It’s 2 extra button clicks to generate a password and save it on 1Password, and you never have to leave your current context.
Versus for email OTP you have to switch to your email client, find the email, perhaps refresh a few times waiting for it to come in, click into the email once you see it, highlight the OTP, click copy, then switch back to the app and finally paste. I don’t understand how anybody could possibly prefer it.
However, OneDrive's promise is "save your files and photos to OneDrive and access them from any device, anywhere". Accordingly, the model OneDrive actually exposes to the user is directory trees of arbitrary files containing what, for OneDrive's purposes, are opaque blobs. This leads to all the behaviours you'd expect from a distributed system using such a model, and therefore the trust issues the public has with MS distributed systems.
Regaining someone's trust in a vendor after a bad experience, even for a different product, is very hard.
