Subscribe
Sign in
Sumr tldr - Safari extension
p/tldr-safari-extensionSummarize pages on Safari browser. Instantly copy/share.
Start new thread
Pavel Larionov

Sumr tldr - Summrarize web pages on Safari browser

by•

Instantly summarize web pages with Sumr. Get beyond the headline while saving time. Activate only when needed, right on your Safari browser on iOS, MacOS and iPadOS. All powered by your OpenAI API key.

Add a comment

Replies

Best
Pavel Larionov
Maker
📌
Safari on iOS is almost perfect. The only thing missing - an ability to summarize an article. So I've created a simple extension which can summarize you an article in just 3 taps aA → Sumr → Summarize Since the making of the very first prototype, I was using it every single day, because 1. faster and more reliable than shortcuts 2. right where I need it to be - in my default browser 3. not in my way, but always just 3 taps away from the content I am reading 4. it makes it very easy to share content on social media and messenger 5. better than web clipper - I can store only a short version of the content piece with a URL The app itself is free. It uses your own OpenAI API key, so you pay as you go. Summarization of one article is usually fraction of a cent (I use gpt 3.5 under the hood - it's sufficient for simple summaries). I am not planning to stop developing - advanced features are on the way! Things on my roadmap: - ability to ask a follow up questions - additional and quickly swappable system prompts - neat storage for summaries alongside URLs in the app and more! Let me know what you think! Feel free to try it and and I would appreciate if you would leave a review on App Store with your thoughts and ideas.
Poli 🔥
this is promising 👍
Val
I wonder how SummarizeMe handles the nuance of different writing styles, especially creative or opinion-based pieces. Accurately capturing the main points in these cases can be tricky! Curious to hear your thoughts.
Pavel Larionov
Maker
@p_val you are bringing up a valid and important point. currently the summary makes everything sound neutral, which sometimes may not be what you want as a user. i plan to add follow-ups in order to make it possible to interrogate the source article. so the user can ask “what’s the sentiment of the article” and receive an evaluation. did i answer your question or did you mean something else?
Liam Gordon
Interesting idea that could help save time, especially for news articles for example. Do you have any plans to add customization into the tone or writing style of the summarisations to feel more relatable to how you prefer to consume information?
Pavel Larionov
Maker
@liam_g_ thank you! yes! i plan to add modifiers so that users can switch between summarization style or language of the output.
Albert
congrats on the launch, sumr tldr sounds like a practical tool for quick content digestion. what inspired the specific focus on safari users, and are there plans to expand to other browsers in the future?
Pavel Larionov
Maker
@mashy thanks! there are at least a couple of reasons for "why safari": 1. i didn't find any summarizer for Safari which would satisfy my personal needs (it should not interfere with how content on the page is represented, should not require app-switching, should look neat, should work on iPhone's version of Safari seamlessly). i guess the choice is much reacher on chrome-based browsers, and on many chromium forks summarizer is even built in. 2. i want to put as much as possible into the native app, so that the settings are managed inside of the main app instead of the extension. Safari extensions are built like that by default. Chrome extension would require me to build a web-app to provide user settings. 3. i would like to transition to on-device inference eventually, either through a 3rd party framework or when Apple will make Apple Intelligence SDK to the public so i can utilize an on-device LLM preinstalled on all Apple devices. this way you would not need to add any API keys, summarization would just work indefinitely for free, for all users. while this most probably can be achieved on other browsers, it would require quite a different approach and the experience will vary from user to user a lot based on various factors. that means more problems for the users, more support requests, more bugs etc. 4. handling paid in-app purchases is built in for apps on App Store. as i eventually want to provide advanced features in exchange for a small one-time fee, i want to be close to paying customers, which can make a transaction with a press on a button - no accounts creation, no Stripe or anything else. so i guess these are main reasons i decided to focus on Safari for now. did i answer your question?