When you have workflows that you repeat over and over it’s easier to formalize with something like jido. Ie if you don’t want to type into a checkbox and verify output everytime.
I always thought it was native. You can write extensions using React, yes, but I was under the impression those got compiled to their internal Swift-based UI components
Passwords are terrible UX for old people in my experience. They try use the same password everywhere, but then password complexity requirements mean they can't use the exact same password everywhere, and then they forget which variant they used on which service, so they just end up going through the reset password flow every time they sign in. I am not convinced that's a better UX than them just using their fingerprint or face to login.
You might be interested in https://kloak.app I believe. It's a privacy-first alternative. It's still in early alpha days, but have most of the things set up. Oh, and we’ve got voice channels with screen sharing in beta too.
How do you plan on funding it? Also, the landing page mentions "You own your community data" but it just looks like you own it and allow us to access it?
"Messages are stored on our servers and are technically accessible at the database level , we won't pretend otherwise. Kloak doesn't require email, phone, or personal info to create an account, your identity isn't tied to your messages the way it would be on other platforms.
Our goal is to implement end-to-end encryption for DMs so that even we can't read message content. But we're not there yet, since after all we need to make sure the platform is safe and not to shield illegal content being sent."
This is a message from one of their founders I found while exploring the app.
Came to post this; Ballistol works brilliantly; and can also be used as a leather conditioner, wound dressing, & marinade for carne de cheval, with the addition of some juniper berries and a little rosemary.
reply