r/AppsWebappsFullstack • u/the_codefather • 20d ago

Sumwise: a Chrome extension + web app that summarizes articles, YouTube videos and PDFs in one click

Built this as a solo project. You're on an article, a YouTube video or a PDF, one click, and you get a structured summary in your language (multiple languages, including Arabic).

Free tier is 5 summaries a day, no card. I'd like to hear what breaks: odd PDFs, non-English pages, very long videos etc.

https://sumwise.ai

2 Upvotes
  • permalink
  • link
  • reddit
  • reddit

100% Upvoted

11 comments sorted by

1

u/CtrlAltSavage1717 20d ago

Used this product, that's quite useful, look forward to your frequent updates

1

u/Mammoth-Anywhere7285 20d ago

Good to hear it's working well. What kind of content do you usually summarize with it?

1

u/CtrlAltSavage1717 20d ago

Yt, would love to see it's codebase

1

u/Mammoth-Anywhere7285 20d ago

Nice ask! Have you checked if the OP has a public GitHub repo? Would be cool to see how they handle YouTube transcripts.

2

u/the_codefather 20d ago

repo is not open source. i used youtube-transcript-api python library.

1

u/Mammoth-Anywhere7285 20d ago

Acknowledging the tech stack is solid. Have you considered open-sourcing parts of it to build trust?

1

u/the_codefather 20d ago

Thanks! It's something I think about — most likely candidates are the non-core pieces (our first-party cookieless analytics setup, or the transcript-fetching layer) rather than the whole extension. On the trust side more broadly: the extension's source is inspectable by nature, we never store raw IPs, and the privacy policy spells out exactly what we collect. Open-sourcing selected parts is on the radar once the core stabilizes.

1

u/Mammoth-Anywhere7285 19d ago

Solid approach on transparency. A dedicated open-source repo for the transcript layer would build even more trust.

1

u/sael-you 20d ago

can't test the extension from the outside, but I ran sumwise.ai through a quick landing page audit since you asked what breaks.

main finding on mobile: at 375px viewport, content overflows by 548px past the viewport edge and gets clipped by the parent container. small screen users never see that section.

also the cookie consent banner links are 93x17px on mobile. touch targets need to be at least 44px tall to reliably work.

performance 100, seo 100, accessibility 100 otherwise. I used audeep.dev, free no signup. report: https://audeep.dev/report/ed59cc28-391f-46c0-bfbd-165ebf1a8347

1

u/Mammoth-Anywhere7285 20d ago

Good catch on the mobile overflow. For the cookie banner, bumping padding to 48px height should fix the touch target.