Hey everyone!

I'm an indie developer working on Make Resume, an iOS app that helps people create professional resumes without spending hours on formatting.

The idea is pretty simple: make resume creation faster and less frustrating, especially for people applying for their first job or updating an old CV.

What I've built so far:

I've started to notice something about mature products.

The size of a feature rarely determines how much work it takes.

Instead, the effort depends on how many past decisions that feature touches.

A simple "Add Google Login" suddenly affects authentication, onboarding, permissions, analytics, documentation, QA, and maybe even your pricing model. What looked like a two-hour task turns into a week of discussions because you're no longer building a feature; you're negotiating with decisions your product has accumulated over months or years.

Hey Product Hunt!

As more users adopt the Virtual Card feature for remote and international teams, we ve made some exciting updates to help businesses scale globally:

• Regional spend controls for international teams:

  Issue cards to global teams with regional limits, ensuring compliance and reducing risk.

• Easy card creation for contractors and remote workers:

  Need to issue a card for a new team member? Do it instantly and securely, no matter where they are in the world.

• No interruption when one card is compromised:

  With each card having its own unique number, only the affected card gets frozen, while the rest of your business continues running smoothly.

One of the biggest challenges we've encountered while building FounderFlow is teaching AI the difference between information that's important and information that actually requires an executive's attention.

At first, it seems straightforward: analyze incoming emails, identify priorities, and help founders decide what to do next.

Hi everyone,

A few years ago, Google's algorithm changed and the traffic to my GIF site plummeted. The site lets users customize GIFs from templates that I make (birthdays, holidays, etc)

Since then, I sort of gave up on the site as a lost cause but always looked for other opportunities to use the tech.

This started as a small itch.

My LLM provider (OpenAI, to be exact) gave me one number: total spend, aka a bill. But I wanted to know which function in my app spent more, and why. The code or the summarizer? Obviously the code, right?

There was no way for me to see my usage broken down. So I built a tiny thing for myself: one line after each API call, sending the token counts and a feature name. I only wanted visibility, nothing more.

Then I got curious whether anyone else cared, and went looking. My problem turned out to be the door into a rabbit hole.

Hey everyone!

If you re building a SaaS or a side-project, setting up payments usually means hours of dealing with webhook routing, customer sync logic, and getting locked into one provider.

I built Paycan to fix this. It s an open-source, self-hosted checkout layer.

• No Vendor Lock-in: Switch between Stripe and PayPal without changing your database or application logic (more local payment providers soon).

• Drop-in Simple: Around 10 lines of code to integrate.

• Self-Hosted & AGPLv3: You run it on your own server, keeping full control over your checkout.

Last time I wrote about the small itch: one OpenAI bill, no idea which feature spent it, so I built a tiny logger. One line after every LLM call, sending model and token counts to my endpoint.

That line still exists. So the question I kept asking myself: if the integration is one line, what s an SDK for? (an "SDK" sounded very cool in my head at that time, someone who -before making this product- had no clue what an SDK is btw).

I m building Jeenly, an iPhone app that creates small personal tools from the prompt.

For example, you might describe a tracker designed around your routine, a calculator for a decision you make repeatedly, recipe generator tailored for your preferences, or a simple planner that works exactly the way you want. Jeenly creates the tool, lets you use it immediately, and lets you improve it by describing changes.

To start with, tools have capabilities of using ai and calling public apis, more capabilities (like notifications, image generations) yet to come!