fraromeo

Interesting take. I will dig more into this, I'm pretty sure it would be an interesting feature for potential customers

A better testimonial could never be made <3 Thank you so much for your support!

Btw I'm not affiliated with them at all, just genuinely curious about their approach to identifying these areas.

The article explores the concept of "the color of bits," emphasizing the need to account for the unique context of digital assets and money in revenue recognition, especially in SaaS businesses and video games. It highlights the complexities in treating digital assets as non-fungible and discusses how revenue recognition for SaaS subscriptions and virtual goods must adapt to digital realities. The article also addresses the alignment of game mechanics with accounting standards in this evolving landscape.

Totally agree. I understand his point but can’t do much unless I implement some very complex stuff specifically for mobile (and I’m not even sure it would work safely)

Update - just released a 7 days free trial

Update - Just released a 7 days free trial!

Working on it. I'll let you know. Thanks for the interest!

I'm thinking about it. Would you be more interested in testing the API or see Creduse in action in an existing web app for example? (I imagine testing the api)

I intend it as server to server but you made me think about this specific case. I might have found a solution that bypass and solve the problem you are referring to but I need to deeply think about it. Not only needs to be secured the API Key (which is solved by the solution I have in mind), but also the content/payload of the request (otherwise the client would change the amount of credits).

Very interesting point. Thanks for bringing this up.

Couple of questions: shouldn't my customers be taking care of this since I don't know their architecture? I think mobile devs can hugely benefit from Creduse, can you point me on how to support them for this scenario?

open to discuss via email if you prefer: francesco@creduse.com

BTW this would exactly your case https://doc.creduse.com/use-cases/payasyougo.html

This is a great question. I'm actually working on it. In the meantime in the documentation there is a section called "Use cases" - here's the pay as you go model for example: https://doc.creduse.com/use-cases/payasyougo.html

I want to implement Creduse into a free ai character chatbot I've created in the past (hellspitching .com) to showcase its use.

Hey there! Thanks a lot! Of course, it would work also on mobile apps. As long as you can make an http request to api.creduse.com/endpoint, you can run it wherever you want :) In your case if the user's payment is completed you can send a POST request to /add with the amount of credits you want to add. The user then, will receive his credits. That's it.

You can find a lot more details on doc.creduse.com

It's possible to use cycle and payg in combination, it's exactly the strength of Creduse.

About the `get-active-balance` endpoint - you're right, it's pretty basic at the moment. It just gives you the total active balance and user ID. It doesn't break down cycle vs PAYG credits or show cycle dates yet.

I've add it to the top of my pipeline. I'll be working on improving this endpoint to give you more detailed info about the user's credit balance.

Regarding the option to choose which credit type to subtract from, I'll keep this in mind and consider its feasibility. Can't promise anything on this just yet, but I appreciate the idea.

I really like your suggestions though! It's exactly the kind of feedback I'm looking for. Thanks for bringing this up, and thanks for subscribing!

Great! Thanks for giving Creduse a try.

By "handled the buying of additional payg credits" do you mean the payment processing?

In October 2022 I started Pitch Deck Studio, an agency that helps startup founders create winning pitch decks. Over the past year, I had the privilege of working with many different clients, attending numerous meetings. I've seen a lot of startups and pitch decks, and I've learned a lot about what works and what doesn't.

Sometimes, though, I wished I could say the harsh truth to my clients. But I couldn't. I had to be professional.

5 months ago then, I decided to build an AI-powered assistant that could do the dirty job for me. An assistant that could tell the truth, no matter how harsh it is, and help founders build a better startup.

I knew almost nothing about coding but I was determined. So I started learning Python, and then HTML, CSS, and JavaScript. I spent hours and hours learning, coding, and testing.

After months of hard work and dedication, here's Hell's Pitching. A chatbot that helps startup founders brainstorm their ideas in a different way.

What you'll get is not the typical 'pat on the back' kind of feedback. What you'll get is a ruthlessly honest AI-powered assistant you need to build a better startup.

Underneath the roast, though, there's wisdom that often leads to 'aha' moments.

So if you think you have a golden startup idea, give Hell's Pitching a try. It's free. And it's fun.

PS I'm ready to get roasted from you guys!