<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Steve Joseph on Medium]]></title>
        <description><![CDATA[Stories by Steve Joseph on Medium]]></description>
        <link>https://medium.com/@futuretomorrow_?source=rss-50d49ec681c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*y3ebMTRpSTNipquWiVSnEw.png</url>
            <title>Stories by Steve Joseph on Medium</title>
            <link>https://medium.com/@futuretomorrow_?source=rss-50d49ec681c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 18:37:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@futuretomorrow_/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[What’s going on with Loveable credits? A solution…]]></title>
            <link>https://medium.com/@futuretomorrow_/whats-going-on-with-loveable-credits-a-solution-b144228fee84?source=rss-50d49ec681c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/b144228fee84</guid>
            <dc:creator><![CDATA[Steve Joseph]]></dc:creator>
            <pubDate>Sun, 10 May 2026 22:50:41 GMT</pubDate>
            <atom:updated>2026-05-11T03:43:28.255Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PTbASL55PEZNg5Vw6AQndw.png" /></figure><p>The problem with Loveable and most vibe coding platforms is that for errors and deletions, it comes out of the user&#39;s credits, even if Loveable admits to the issue being on its end.</p><p>In my humble opinion, a better way to approach this would have been for vibe-coding platforms to have a pool of credits that they control. When an error, deletion, or unintended rollback by Loveable happens, there is an easy process to “reclaim my credits.”</p><p>This would be a series of agents that look at the prompt being disputed and decide whether the error is the result of a bad prompt or a system error.<br>If it’s a system error, credits are pulled from the pool to correct the mistake.</p><p>With this solution:</p><p>1. The user gets the intended result without having to spend more of their credits to fix an issue that was no fault of their own.<br>2. Loveable, as they burn through credits in the pool, will be incentivized to fix the underlying issue(s), as it’s not sustainable for them to keep burning credits and deplete the pool due to underlying issues in how the platform works. <br>3. This establishes or solidifies trust as users will quickly realize Loveable has their back on these issues, and they don’t have to worry about burning through their own credits for issues that again, are no fault of their own.</p><p>Make no mistake, Loveable is valued at a staggering $6.6 Billion USD. As the product has matured, it&#39;s time to go beyond 5 free credits a day and address the underlying concerns pushing users to cancel their subscriptions and seek alternatives such as Claude Code, Claude Design, Cursor, or other solutions.</p><p>The last data I saw in Q4/2025 stated Loveable had over 180,000 paying customers. Again, a staggering number. However, unless these underlying credit issues are addressed, Loveable will eventually find themselves in a position of stagnation during a period where almost anyone can vibe code a website or app due to the proliferation of AI and its capabilities.</p><p>While this article is specific to Loveable, I firmly believe any competitor that addresses these issues with a pool or similar solution is going to win the vibe coding platform race.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b144228fee84" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>