Michael's Feedback

Facebook Browser Ejection Strategy

The specs must be very clear on how exactly ejecting from Facebook happens. There are two possible approaches:

Option A: Session-Based (Anonymous → Link)

• Create a session stored on the backend during the quiz/funnel.
• Give the user a specific link that opens that session in the mobile web browser.

Option B: Account-Based (Sign Up → Login Link)

• Create the actual user entity during a sign-up process using email or phone number.
• Give the user a link that logs them in via mobile web browser.

Considerations for Option B

• Google Sign-In won't work — users are not signed into Google inside the Facebook browser, so "Sign in with Google" will fail and block users who rely on it.
• Password risk — if the user creates a password inside the Facebook browser, they may not remember it later and will have to go through password reset.

Ejection Destination: Mobile Web vs. Native App

• We need to decide whether we're ejecting users into mobile web browser or into the native app.
• The native app does not support automatic login via a login link — if we tell users to download the Twofold app, they'll have to either sign in with Google or enter email/password manually.
• We cannot quickly build a flow that carries the session from the Facebook browser into the native app.

Key Decision

Each option has pros and cons. We need to weigh them and decide where in the funnel exactly we eject from the Facebook browser — and into what (mobile web vs. native app).

No Credit Card Early in the Facebook Funnel

Given that we're focusing on the Facebook funnel (users arriving from Facebook ads), we should not consider any funnel variants that take a credit card early in the process. The flow should be:

1. Show great value first.
2. Eject from the Facebook mobile browser into a desktop or mobile browser.
3. Only then, at some point, take a credit card — this also gives better signal to Facebook.

We need to be very deliberate in allowing Facebook reporting to work correctly. We need to give Facebook as many signals as possible about what the user is doing — both inside the Facebook browser and after ejecting.

Design Consistency with the Twofold App

The current onboarding in the Twofold app resembles the website (www) but is completely different from the actual app the user lands in. For the new Facebook funnel, we should align the design to how the actual application looks to maintain consistency. This is more important than modernizing the color scheme.

• Choose colors that are similar to the colors used in the app.
• Slight changes to fonts or colors are fine if we believe they improve conversion ratios, but it needs to feel like the same application.

Simplicity as a Core Principle

• Our users are not tech-savvy. They struggle with too many options.
• Users have told us that one of the things they appreciate most about Twofold is simplicity.
• We need to maintain that simplicity. We need to be laser-focused on what we do and what we do very well.

Quality as a Differentiator

• A lot of user feedback says we are better than competitors in terms of quality.
• One idea: tell users they can try other apps and we're confident they'll always come back to us.
• Caveat: not sure if this specific idea is good marketing — take it with a grain of salt.

NUX & Activation: Web vs. Native App

• The current NUX greatly improved conversion to activation on desktop web.
• However, it did not improve conversion to activation on the native app. There may be differences between how native app and desktop web work in terms of having a NUX-like experience.
• We can consider whether we want something like micro steps towards activation after onboarding and sign-up are complete — i.e., when the user lands on the /new page.

Alternative Sign-Up Methods

We can consider sign-up methods that don't involve email + password — for example, just collecting the email and sending a login link or a code. However, there are trade-offs:

• Login link — can have deliverability issues (emails not arriving, landing in spam).
• Login code — requires the user to open their email, find the code, and paste it back into Twofold. This can be cumbersome, especially for less tech-savvy users.

Both approaches may introduce friction that outweighs the benefit of removing passwords.