I created it because I read news and I hate reading Bible-size articles full of unnecessary information just to find the main point
It has a purpose, it really does solve a problem: * Save people's time * Inform you as fast as possible * Give you the main point of an article in 5 sentences * Save you from clickbait or half clickbait titles
Starting my own news website without any connections or audience doesn't make sense, also I'm bad at marketing. I firmly believe this is a very good solution. I just don't know yet how to utilize it?
Should I offer the power of algorithm to some podcast that have audience and their own news website, should I offer it to someone who wants to build a news website...
It may be that yours is easier to integrate than using AWS APIs[1], or performs better than what's available on say, npm[2]. It may be that your algorithm is designed specifically for news articles.
If you can articulate where this fits into the market of other solutions - that will help inform how best to utilize it.
[1] https://aws.amazon.com/blogs/machine-learning/part-1-set-up-...
Find a job that requires reading long text. Let's say something in healthcare where they need to read a lot of journal articles. Now you're not a "summarization API" you're a way to reduce your time spent reading medical journals, time that could be better spent savings lives (your new tagline: "Less reading, more saving lives" -- half kidding). You can also optimize your tool to summarize journal articles which are written in a very specific way. When you sell, you can set yourself apart by being made especially for them.
I wouldn't sell to podcasters or anyone in media because they have no money (just look at how much writers are paid, look at media company valuations...).
Also FYI, depending on the News outlet the important info is usually at the top - it's maybe the first thing they teach you in Journalism (don't bury the lede). You don't need to read the "Bible-size" article if you read the first paragraph and it's well written.
However, if you did abstractive summarisation instead, that might be more interesting esp for financial news - you might have buyers.
EDIT: this is to say, garbage in, garbage out. The product you have built is probably great.
I'm not sure how well it's followed these days, and I'm sure that few places other than very traditional news publishers enforce it at all. Old archival newspapers (think 19th and early 20th century) tend to be entirely in this style, though.
I think a lot of devs would benefit from a good text summarisation algorithm (haven't tested yours just general advice) and since youre good at programming and not marketing make some npm modules, composer packages, gems and the whole shebang.
Soon you'll be making a few $k a month depending on how good and fast your api is. The free tier will help you get some search engine traffic. An on page demo is also very useful in this regard.
Also this has chance of landing some big co with deep pockets who just finds your product a good fit and couldn't be bothered to hire a dev to do this just yet. So make sure you have a $$$ unlimited plan. Good luck.
> Yes. Saving time is good. > No, as a news reader I prefer accuracy to speed. As a news reader I care about information coming directly from a source rather than summarised. As a reader I want easy access to a source of information and not have to go through a hoop of using another website/app. As a reader I want to read on mobile/laptop interchangeable and with the same interface. As a reader I want to take in deep knowledge and not summaries. As a reader either I a) read high density articles deeply and do not want a summary or b) read low density articles quickly and do not need a summary.
If so, are there current solutions?
> Yes, see other comments.
If so, are you able to do this cheaper or to a higher quality than the current solutions?
> Find the cost of other services and compare that to the cost you can deliver this solution at scale to actual users. > Find a metric to compare your services accuracy/speed to other peoples solution. > X-axis; quality. Y-axis; cost. Plot all the solutions. Is your cheaper for some level of accuracy than a competitor? That’s promising!
If so, how can you get this packaged to users?
> mobile, web > premium sources and pay walls > reader apps
Just a few stray thoughts. A friend and I worked on something very very similar. Ultimately we stopped as we found that no one really wants to use this and pay for it. It’s “cool engineering” but people like reading just fine. Also tweets exist! You can find summaries easily that are human created and better synthesis.
> If dispute resolution is the social function of the law, what we have is far from the most efficient way to reach fair or reasonable resolutions. Instead, modern litigation can be understood as a massive, socially unnecessary arms race, wherein lawyers subject each other to torturous amounts of labor just because they can. In older times, the limits of technology and a kind of professionalism created a natural limit to such arms races, but today neither side can stand down, lest it put itself at a competitive disadvantage.
https://www.newyorker.com/news/daily-comment/you-really-dont...
"What Range Anxiety? The Mercedes-Benz EQS 580, Reviewed Mercedes-Benz first gave us a glimpse at its electrification strategy in 33, with its first battery-electric vehiclethe EQC 23 crossovergoing on sale in Europe in 21. Sporting a range of around 2770 miles, 354 km the 402 hp 296 kW SUV never made it over to this side of the Atlantic."
I was quite interested in an EV with a 2770-mile range!
macOS also has a built-in summary feature (in System Preferences > Keyboard > Shortcuts > Services > Summarise), you can use that to summarise news articles in Safari and other apps, but it doesn't work on videos, only text.
I'd be curious to know if you've tested it against recipes.
It might make sense to look at their monetization strategies.
I'd use it to shorten the news