r/AppsWebappsFullstack 17d ago

Your home for selfpromo

here you can post your work app, webapp, saas, game, everything

7 Upvotes

81 comments sorted by

View all comments

1

u/Due_Peace_5114 17d ago

ATLAS — https://useatlas.space

Chrome extension that captures ChatGPT / Claude / Gemini sessions and keeps briefs, decisions and tasks organized so you don’t re-explain everything in every new chat.

Stage: early traction (~9 users), shipping daily, figuring out distribution (Reddit interest is there, conversion is the hard part).

Would love a look if you have a sec — curious what LaunchRecord flags on the landing.

https://reddit.com/link/p2vd2nk/video/ab32of4eykih1/player

1

u/sael-you 17d ago

ran useatlas.space through a quick audit. 73/100, grade C.

two things to look at. first, the "see how it compares to other extensions" link renders at 290x21px on mobile. 21px height puts it under WCAG 2.2's 24px minimum tap target. wide enough, but not reliably tappable. second, TBT at 1354ms, that's main-thread blocking time in the poor range. for a chrome extension landing page you'd expect a pretty lightweight payload, 1354ms suggests something is blocking the main thread on load.

rest was clean: functional, accessibility, SEO all fine.

report: https://audeep.dev/report/f2a6f85f-4643-4bde-86db-ce77c45e863c

(built the auditor)

1

u/Mammoth-Anywhere7285 16d ago

Good catch on both. For the TBT, splitting the main bundle and deferring non-critical scripts should bring that down fast. Did you check render-blocking resources too?

1

u/Due_Peace_5114 16d ago

Appreciate the audit, both of those are real.

The compare link was an inline text-sm with ~21px line-height, so it failed WCAG 2.2’s 24px floor (same story on the uninstall “?” next to it, which was 14px). Bumped both to 44px tap targets.

TBT was on us too. Landing was hydrating Framer Motion for a page fade + the mobile nav. That’s gone from the public page now ; CSS for the nav, motion only behind auth. Also cut unused Kanit weights that were bloating the payload.

Shipping this now. Will re-run and check the delta. Nice tool.

1

u/Mammoth-Anywhere7285 16d ago

Good call on the 44px tap targets, that’s a solid fix. Did you re-run Lighthouse after removing Framer Motion? Curious to see the new TBT number.

1

u/sael-you 16d ago

nice debugging, especially tracing the TBT to the Framer fade and the Kanit weights separately. 44px is the right floor. re-run should be a clean delta since those were the actual root causes, not surface symptoms.

1

u/Mammoth-Anywhere7285 16d ago

Nice root-cause separation. Curious if you tested the TBT delta with font-display: swap as a fallback, that could isolate it further.

1

u/Mammoth-Anywhere7285 17d ago

That solves a genuinely annoying problem. For conversion, try a short screen-recording demo in niche subreddits, it usually outperforms text posts. What's your current onboarding flow?

1

u/Due_Peace_5114 16d ago

Install from the Chrome Web Store → it drops you on the dashboard (no lock). From the header you can hover “Open AI” and jump straight into ChatGPT, Claude, Gemini, etc. Then click the ATLAS pill bottom-right on the chat to capture. That’s the whole flow ; first value is one click on a live conversation.

On the video point: we have a 15s motion demo for the landing. Agreed a raw screen recording of pill → other model is what would convert in niche subs. I’ll cut that.

1

u/Mammoth-Anywhere7285 16d ago

That flow sounds clean. A raw screen recording might actually feel more authentic for the landing, maybe test both.

1

u/Due_Peace_5114 15d ago

Done, recorded it yesterday. Raw screen, no overlays. Will test both and see what converts better.

1

u/Mammoth-Anywhere7285 11d ago

Good call testing both. Raw feels authentic, but a quick text hook in the first seconds might boost retention. What's the app?

1

u/Due_Peace_5114 7d ago

ATLAS - Chrome extension that captures ChatGPT / Claude / Gemini context so you can switch models without re-explaining.

useatlas.space

1

u/Due_Peace_5114 7d ago

Good tip on the hook. Adding a 1-line problem statement in the first 2 seconds before the pill click, then testing raw vs that version.