Introducing Halo — the habit app with an AI coach.
It's like James Clear in your pocket.
Turn your good intentions into life-changing habits.
Now available on the App Store:
https://t.co/wKnBzK6U4v
@joshsnow@mq_p We love backend workflows and use those as appropriate. In this particular case it's better to perform most of these actions on the page for performance reasons. The one exception is checking phone number verification code - that's performed on the backend for security reasons
@joshsnow@bestnoodldev so this particular UX doesn't have a full onboarding process (because most apps don't need that) but it does have several steps: 1) collecting email/pw 2) collecting basic data like name (which you can whatever other fields you want to) 3) optional email/phone verification
@joshsnow@JJEnglert@joshsnow@JJEnglert while we think green is a lovely color, the purpose of all of these being the same color is to differentiate system workflows from workflows later added by devs (since those will be blue)
@joshsnow We're always open to feedback if you see something that is slow, seems unnecessary, or clunky. Perhaps you and I can do a call, walk through the template to get your feedback, and then you can re-assess?
@joshsnow One example is phone/email verification - it's a really common feature but it's actually quite tricky to build. Canvas allows you to turn it on with a single click (but it adds some workflows to the page).