If you’re interested in this area I highly recommend “The Vital Question” by Nick Lane if you haven’t read it.
The TLDR of his theory is that life originated in alkaline hydrothermal vents on the ocean floor, where natural energy gradients could have driven primitive metabolic reactions before the development of DNA.
Book goes into a lot of layperson-accessible detail.
I think it really depends. I agree that the prototypical pop something up in your face that forces you to interact with it and blocks your usage of the product make your product harder to use.
But stateful experiences don't inherently suffer from this problem. Checklists, embedded cards, context specific empty states, e.g. can all make products easier to use, and don't get in users' ways. And what someone should be shown should look different if they're in an empty product they need to setup, vs an experienced user that's very familiar with the product. Not treating these distinctly means you're compromising the experience for someone.
I do agree that keeping track of journey state in analytics tools, and getting that data to go to market teams are crucial too, but they won't make your product easier to use.
I gave up the moto when my wife and I started trying for a kid, and this is by far the thing I miss most about it. Instant mental clarity on demand. I bike a lot now but the lower stakes mean it's not quite the same.
We're taking the same developer-centric approach to onboarding at Dopt and this really is fundamentally different than the existing tools (Userflow, Pendo, Appcues, etc...).
We are a Seed stage company (raised 5.1M) building a set of APIs and SDKs that help developers create tailored product onboarding, feature discovery, and announcement experiences — all while enabling their entire team with visibility and control to orchestrate who should see what, when. You can read more about why we started Switchboard here https://blog.switchboard.cc/announcing-switchboard
We're hiring for engineers based out of our Oakland office (hybrid, at least two days per week in our office right across the street from the Fox theater). We're a team of eight and are looking to bring on another one or two engineers over the next couple of months.
We're a TypeScript and Go shop. The closed-source bits live in a polyglot monorepo that leverages yarn workspaces heavily. We support local and dockerized development to provide a first-class developer experience regardless of what you develop on Mac or Linux. Our platform is built on NodeJS, React, PostgreSQL, and OpenAPI.
We're offering generous equity, 10-year exercise windows, and the option to early exercise to everyone. We think this is the most flexible and inclusive approach! We've also pledged 1% of our company's equity to charity through pledge1percent.org
We're currently prioritizing the following roles (but we'd love to hear from you even if you don't fit neatly into any of them):
We are a Seed stage company (raised 5.1M) building a set of APIs and SDKs that help developers create tailored product onboarding, feature discovery, and announcement experiences — all while enabling their entire team with visibility and control to orchestrate who should see what, when. You can read more about why we started Switchboard here https://blog.switchboard.cc/announcing-switchboard
We're hiring for engineers based out of our Oakland office (hybrid, at least two days in the office per week). We're a team of eight and are looking to bring on another one or two engineers over the next couple of months.
We're a TypeScript and Go shop. The closed-source bits live in a polyglot monorepo that leverages yarn workspaces heavily. We support local and dockerized development to provide a first-class developer experience regardless of what you develop on Mac or Linux. Our platform is built on NodeJS, React, PostgreSQL, and OpenAPI.
We're offering generous equity, 10-year exercise windows, and the option to early exercise to everyone. We think this is the most flexible and inclusive approach! We've also pledged 1% of our company's equity to charity through pledge1percent.org
We're currently prioritizing the following roles (but we'd love to hear from you even if you don't fit neatly into any of them):
We are a Seed stage company building APIs / SDKs / libraries for developers - more specifically growth engineers - to make it much easier to build robust growth experiences (e.g. onboarding experiences meant to drive activation, contextual nudges to drive feature engagement, etc...). These tools will enable their less-technical (or non-technical) cross-functional counterparts to craft growth journeys that determine who sees what, when.
We're hiring for engineers based out of our Oakland office (hybrid, at least two days in the office per week). We're a team of eight and are looking to bring on another one or two engineers over the next couple of months. We're offering generous equity, 10-year exercise windows, and the option to early exercise to everyone. We think this is the most flexible and inclusive approach.
We're currently prioritizing the following roles (but we'd love to hear from you even if you don't fit neatly into any of them):
The TLDR of his theory is that life originated in alkaline hydrothermal vents on the ocean floor, where natural energy gradients could have driven primitive metabolic reactions before the development of DNA.
Book goes into a lot of layperson-accessible detail.