Two Balances, Not One: Reading Rork's Build Credits and Cloud Credits Apart
Rork keeps two separate balances. Here is how to tell which one a charge came from, why one prompt can cost more than one credit, why a Cloud balance that never moves may mean your AI is not running at all, and what changes once real users start spending it for you.
Rork's Free Tier Gives You 35 Credits a Month, but the Number That Shapes Your Work Is 5 a Day
Rork's free plan is 35 credits per month with a 5-credit daily cap. The daily cap, not the monthly total, decides how you work. Here is how I spend those five, what I verify off-credit, and where the free tier stops.
Rork Max Credits Drain on Rework, Not Features — Where to Let AI Run and Where to Finish by Hand
Rork Max credit usage is driven less by how complex your app is and more by how many times you regenerate a screen. Here is a practical way to decide what to hand to AI and what to finish by hand, from an indie developer who ships to the stores solo.
Designing Rork Max Iterations So You Don't Burn Through Credits
Rork Max generates native Swift for you, but regenerating on impulse drains credits astonishingly fast. Estimate how many regenerations each screen will take, separate structural prompts from polish prompts, and draw a clear line for what to hand-edit instead. From an indie developer who ships to the store, here's how to treat credits as a budget.