Read on Twitter
Candidate for #BuildInPublic this weekend-
Currently parents can start the process to enroll their kids at a school in @everyoak anonymously. Changing it so that parents have to create an account first. This hugely simplifies the admission workflow and saves hours for schools!
Currently parents can start the process to enroll their kids at a school in @everyoak anonymously. Changing it so that parents have to create an account first. This hugely simplifies the admission workflow and saves hours for schools!
Can I build just like one feature in public and not the entire product? Is that allowed?
First some context- why does enrollment not req registration?
Web-based enrollment is a keystone feature. It was the entire MVP.
Form -> Zapier -> Airtable / Slack / email.
Additional features were built around it. Enrollment is used once a year. Very low ROI to change it.
Web-based enrollment is a keystone feature. It was the entire MVP.
Form -> Zapier -> Airtable / Slack / email.
Additional features were built around it. Enrollment is used once a year. Very low ROI to change it.
Once enrollment ends, classes are assigned, parent accounts created, and they’re asked to come pay tuition, fill out emergency info, etc. Thus begins a dance of “Is this the right email or is this parent ghosting the school?”. Requiring registration opens up new possibilities.
Step 1- I need a way for families to register on the site. There is no registration page right now, only sign in! This is easy enough- exact copy of the sign in page but call it sign up. I'm going for functional, not award-winning.
That's all I am doing tonight. Time for sleep.
That's all I am doing tonight. Time for sleep.
Basically took a weeklong break from this because life, but I'm back at it again.
First contentious thing I've done is get rid of the password box. You don't need a password to signup. Instead you click on the verification email sent to you.
First contentious thing I've done is get rid of the password box. You don't need a password to signup. Instead you click on the verification email sent to you.
Registering for an account sends you an email with a link that automatically log you in to your account.
At this point people can sign up and get logged in. I need to now focus on the onboarding experience, which is basically the page to tell them-
“hey- the following schools have online enrollment starting ______. Come back here on ______ to enroll your kid(s).”
“hey- the following schools have online enrollment starting ______. Come back here on ______ to enroll your kid(s).”
Took this opportunity to redo the navbars. I had noticed that the app was sending out a TON of "magic links" (emails with auto-logic urls) to users, and I wondered whether people weren't figuring out that they could set a password, or if they truly preferred login links.
Then a user wrote in a couple weeks ago asking how to change her password and I realized it was definitely poor UI design. Whoops.
I have a hard deadline to finish rebuilding this feature. Enrollment begins January 4.
Small diversion to this @alexhillman tweet about building in public vs learning in public: https://twitter.com/alexhillman/status/1342268073802407944?s=20
Small diversion to this @alexhillman tweet about building in public vs learning in public: https://twitter.com/alexhillman/status/1342268073802407944?s=20