CHRISTIAN ONOCHIE

I was thinking about old times where subscriptions were uncommon thing and mainly there was one time paywall. Users just don't mind paying few dollars for every app monthly, which in sum up can be equal to hundreds of dollars, or there isn't any solution for this at all? App developers are chasing money, they don't want to publish their work for just lame one time pay from one user. They want to get from user as much as it possible, logical way to that is by subscriptions. Also what about privacy, every app nowadays has to sell your data for additional money. There are no longer solutions connecting one time paywall with leaving data on Your device. My point is, does it make sense to create new apps more like everyday use so for some people It will be trip helper or sleep sounds so they can sleep better and for others it will be some advanced grocery list etc. with some cool features behind one time paywall and without selling data.

Hey Product Hunt, Parsons here, founder of PodcastorAI.

A few days ago, we launched PodcastorAI and finished as the #3 Product of the Day. We ve received more than 300 upvotes and 100 comments so far, and I m incredibly grateful to everyone who tried the product, asked questions, or shared feedback.

The one where the email is already downloaded before you click it. Turns out the fastest way to fetch a message is to have fetched it earlier. Nobel committee, we're waiting.

Faster

• New mail arrives with its body attached. When a message lands, Skim quietly pulls the body onto the fetch connection right away newest first, small ones only, three at a time. So tapping that notification is now a read from your own disk instead of a chat with the server.

• The connection wakes up when you do. Alt-tab back to Skim and it logs in and re-selects your inbox in the background, so your click pays for a FETCH and nothing else. Costs precisely zero when everything's already warm.

• Waking from sleep no longer confuses OAuth with itself. All connections now share one token cache, so two of them can't sprint for the same rotating Microsoft refresh token at the same time and both lose.

• Token requests got a timeout and a reused HTTPS client. Previously a black-holed auth endpoint could hang around for as long as Windows kept the socket alive. Now it gets 15 seconds and then it's out.

• Discovering a dead connection dropped from ~22 40s to ~4 6s. One tiny NOOP up front instead of twenty seconds of staring at "Loading ". Bold, we know.

Fixed