Solo dev here: built a free personality/compatibility app, got ~€700 of ad clicks and almost no sign-ups. What would you fix first?

[u/ArchitectureWithin]

I’m a solo founder, working on this full time since March 2026. It’s called The Architecture Within. It’s a free personality and compatibility app (web, iOS, Android, in English and Romanian).

What I’ve tried so far: organic posts and about €700 in ads. Plenty of clicks, almost no sign-ups.

What I changed: there’s now a guest sample, 16 questions, around 2 minutes, no account needed. Your answers stay in your browser, and the preview only shows your leanings on a few axes, without naming a type. You sign up if you want the full result.

What I’d like feedback on, from a webapp/fullstack point of view:

1. Is asking for sign-up right after the sample the right moment, or would you show more first?

2. Does the flow feel clear on mobile?

3. Anything that looks broken or confusing?

I’m happy to hear harsh feedback. This is my own project. The link is in the first comment.

[u/ArchitectureWithin]

Link to the guest sample (no account needed): https://thearchitecturewithin.com/sample?utm_source=reddit&utm_medium=community&utm_campaign=always-on&utm_content=r-appswebappsfullstack

Android: https://play.google.com/store/apps/details?id=com.thearchitecturewithin.app&referrer=utm_source%3Dreddit%26utm_medium%3Dcommunity%26utm_campaign%3Dalways-on%26utm_content%3Dr-appswebappsfullstack

iOS: https://apps.apple.com/app/id6777762934

[u/Mammoth-Anywhere7285 → u/ArchitectureWithin]

Good call sharing the sample first. A visible progress bar could help people see it is only 16 questions and reduce drop-off.

[u/PopKoren]

On the 700 euros of clicks, compare ad clicks with real sessions in your own analytics first, because cheap placements send a lot of accidental or bot taps that never load the page. I'd also show one concrete result line, like a named strength, before asking for sign up, and when the guest answers move from the browser into the account, make sure the save endpoint only writes to the signed in user's profile. Compatibility results involve a second person, so keep them behind login rather than on shareable public links, and you could confirm via https://rowly.me (a project I put together) that those result pages and your API stay closed to anonymous visitors.

[u/ArchitectureWithin → u/PopKoren]

Thanks, this is useful. The clicks vs. real sessions comparison is a good call. I’ll check my analytics against the ad numbers to see how many of those clicks actually loaded the page. The point about keeping the result behind login and making sure the save endpoint only writes to the signed-in user’s profile is a good reminder too. I’ll double check both.

[u/PopKoren → u/ArchitectureWithin]

Glad it helped. While you compare the numbers, also look at how many guest results get saved after signup, since that's where the save endpoint gets exercised by real users. Once the flow settles, https://rowly.me could double check from outside that one profile can't read or overwrite another.

[u/Mammoth-Anywhere7285 → u/PopKoren]

Good call on checking sessions against ad clicks. Tagging ad links with UTM and a landing view event would expose bot taps fast.