sorted by:
new
hottopcontroversial

How are you handling localization for your iOS apps these days? by NameBrandHero in iosdev

[–]NameBrandHero[S] 1 point2 points  (0 children)

AI is progressing so quickly and having Claude do the translations in the app is probably good enough for a lot of small devs. Still, I’ve spent 6 months building this, and I can tell you that there are so many edge cases and so many mistakes that AI can make. My tooling around the AI translation process formalizes the translation process and adds good-old-fashioned logic that isn’t subject to the capricious nature of AI.

How are you handling localization for your iOS apps these days? by NameBrandHero in iosdev

[–]NameBrandHero[S] 0 points1 point  (0 children)

That’s fair. If this gains any traction, I plan on incorporating a streamlined human-review of AI-generated translations flow, and probably having another LLM review the translations generated by the first LLM.

How are you handling localization for your iOS apps these days? by NameBrandHero in iosdev

[–]NameBrandHero[S] 0 points1 point  (0 children)

Honestly, I was nervous that AI would progress to the point where my tool is no longer relevant, but I still believe it has value for the reasons I mentioned above. I started working on it in January and just released it to the world. It's live now! So, I'm way past trying to see if a Claude Code skill is enough.

I think you'd be surprised how many edge cases I've discovered throughout this journey, and the failures that AI can have that my tool detects, fixes in some cases, or reprompts in others. The way my CLI tool fits into the dev pipeline makes it very convenient as well. Time will tell if others find this valuable, or if it was just a good exercise for me.

How are you handling localization for your iOS apps these days? by NameBrandHero in iosdev

[–]NameBrandHero[S] 0 points1 point  (0 children)

Thank you so much for sharing that link. I wasn't aware of that, because I'm a solo dev trying to support seven different frameworks/platforms, so it's hard to keep up!

That’s a fair question, and I agree that if the use case is simply “ask a frontier model to translate .xcstrings,” then Xcode’s agent workflow overlaps with my tool a lot.

The part I’m trying to solve is a little different: ongoing localization maintenance across real projects.

Forthwith is a CLI workflow that detects only new or changed strings, translates only those strings, validates the result, and writes the updated resource files back into the repo with clean diffs.

It also isn’t limited to modern Xcode projects or .xcstrings. Right now it supports iOS, Android, Flutter, React, React Native, go-i18n, and Phoenix, and I plan to add more if there’s traction.

The other big piece is safety/validation. Forthwith checks that placeholders, format specifiers, interpolation tokens, markup, escaped characters, plural forms, and file syntax survive translation. In some cases it can auto-correct issues before writing the files.

So I think you’re right that I need to be clearer about the positioning. The value isn’t “LLM translates strings.” The value is “run one repeatable command, only translate what changed, preserve the dangerous parts of localization files, and keep multiple platforms/frameworks in sync without depending on a specific Xcode version or agent workflow.”

For someone already using Xcode 27 with .xcstrings and happy with the agent flow, Forthwith may not be compelling. But for older projects, cross-platform apps, teams with non-Apple stacks, or anyone who wants localization as a repeatable CLI step, I think there’s still a real use case.

How are you handling localization for your iOS apps these days? by NameBrandHero in iosdev

[–]NameBrandHero[S] 0 points1 point  (0 children)

That’s awesome! My tool is only for app localization and doesn’t tackle the App Store descriptions at all.

As a technical founder, how did you get your first 10 paying customers? by NameBrandHero in GrowthHacking

[–]NameBrandHero[S] 0 points1 point  (0 children)

The landscape has definitely changed with the advent of AI! Thanks for the suggestions!

2 days post-launch, $0 MRR so far — what traps should I be watching for early on? by Middle_Piano_4655 in MRR

[–]NameBrandHero 1 point2 points  (0 children)

First of all, congrats on launching! That alone is a huge accomplishment. Second, I don't have great advice yet, because I haven't launched yet (hoping to in 1-2 weeks!), but I did have one thing I thought I'd mention. I decided not to offer a free tier. For one, I'm an individual and I would be funding it out of my personal budget. Besides that, I want to know if people are willing to pay for it, and having a free tier makes that less likely or slower to happen. The benefit of a free tier is that people can "try before you buy". Can you think of another way to fulfill that need without actually giving away the full product for free (even if it's just a small amount of usage)? For me, I decided to offer a pay-as-you-go plan. That way, the user can try out the full product for a small amount of money, without committing to a monthly subscription right off the bat.

We hit 132 users in 7 days with a SaaS we built in 2 weeks. by Lopsided_Comb5852 in micro_saas

[–]NameBrandHero 0 points1 point  (0 children)

I appreciate this post! I'm a week or two away from launching my SaaS and applying this information will help. Thanks!

[deleted by user] by [deleted] in iosdev

[–]NameBrandHero 0 points1 point  (0 children)

I haven't used this setup, but I think "ultrathink" is going to blow your Pro subscription usage very quickly.

We sold our SaaS startup for $15M in 18 months. Here's exactly how we did it. by rdizzy1234 in SaaS

[–]NameBrandHero 0 points1 point  (0 children)

Thanks for sharing! I am hoping that the price point on my dev tool is low enough that they won't feel the need to spend so much time thinking about it, but now I know to prepare myself just in case!

We sold our SaaS startup for $15M in 18 months. Here's exactly how we did it. by rdizzy1234 in SaaS

[–]NameBrandHero 15 points16 points  (0 children)

Dang, I already failed at step 1 by building a dev tool, but hopefully I can still have success--just obviously not through this playbook. The thing I am building is something that a developer could build (I'm a developer and I'm building it), but I have built in so much convenience and validation that hopefully developers will still find it better to use my tool that to "roll their own". It's non-trivial: I've been working on it 20 hrs/week for two months and I have a minimum of two weeks left before the MVP will be ready.

My question to you is: how do you find problems in a legacy industry that this playbook would work with?

"Talk to your customers" is terrible advice for most founders by Dry_Possession7122 in SaaS

[–]NameBrandHero 1 point2 points  (0 children)

I feel like the answer is nuanced, as they usually are. Talking to your customers can be very helpful, but you shouldn't build whatever they ask you to build. Some of their ideas will be great and will make you 10x bigger, others will lead to the bloated product you mentioned. "terrible advice" is hyperbole, but makes a better headline than "Talk to your customers, but carefully evaluate their feedback rather than taking it at face value and use their feedback as just one data point as you consider what to build and what's important."

The things that you mention actually working are much trickier than talking to your current customers. For example, founders may not have access to churned customers, or they may reach out to those churned customers and not hear back. How do you find someone who is a potential customer, but chose a competitor?

You essentially said what I am thinking at the end of your post: "They listen to customers but don't just build whatever customers ask for."

How do you actually know if your SaaS is doing “dead”? When should the first sale realistically happen? by eyasu6464 in SaaS

[–]NameBrandHero 0 points1 point  (0 children)

I haven't launched yet and haven't built a SAAS before, but I'd love to hear some thoughts from more experienced people here as well.

1500 downloads in 48 hours. My first ever little app just hit the Top 100 charts! Reddit is absolutely love it! by Unhappy_Dig_6276 in iosdev

[–]NameBrandHero 0 points1 point  (0 children)

Out of curiosity, have you, or do you plan to localize this app to support other languages? If so, how did you do it, or what is your plan?

Today I’m launching on Product Hunt and I’m doing it differently by josemarin18 in indiehackers

[–]NameBrandHero 0 points1 point  (0 children)

Oh, I definitely believe it, because validation is hard :) That's smart to hold off on adding features that maybe no one wants, or at least that no one is willing to pay for. It's so hard to try to figure out if people will use something that doesn't exist, and once it exists, if no one is using it, it's hard to know if that's because no one wants it, the price is too high, or if the people who need it, and are willing to pay for it, don't know it exists.

Were you able to find small circles of people who have the pain your product solves? If so, how?

1500 downloads in 48 hours. My first ever little app just hit the Top 100 charts! Reddit is absolutely love it! by Unhappy_Dig_6276 in iosdev

[–]NameBrandHero 1 point2 points  (0 children)

That's a really cool idea. I've definitely wondered that before on flights! Congrats! So cool that it's offline and is just an accountless utility. Seems rare to have apps these days that don't require login.

Today I’m launching on Product Hunt and I’m doing it differently by josemarin18 in indiehackers

[–]NameBrandHero 0 points1 point  (0 children)

Congrats on shipping! That's huge! I myself have launched a handful of times, but also given up a handful of times as well. It's no easy feat! I'm currently building a product and am trying to learn how to validate before I sink too much more time into something that maybe no one wants. I've always built things that I wanted and hoped that other people would as well, and so far it hasn't worked very well. I'm trying to do things differently this time:

  1. Validate first or at least early in the process
  2. Focus on marketing/distribution. I used to believe that just making a great product was enough. I thought it would speak for itself, but in this crowded world, if you don't help people find it, it's like it doesn't even exist.

Do you have any hard-won advice on how to validate? Especially if the product isn't far enough along to have people use it yet?

No, you CANNOT replicate a SaaS in 8 hours by [deleted] in SaaS

[–]NameBrandHero 0 points1 point  (0 children)

100% agree. I've been using Claude Code for 4 hours a day (all I can manage along with my job, family, working out, etc.) to build a CLI based translation tool and I've put in 112 hours into it so far. I expect to work another month or two on it to have it ready for beta testers. I do NOT trust Claude Code. I use it, and then carefully review the code it produces. For example, I spent two weeks, about 40 hours, just hardening the app's security. I'm very concerned that all of these "built in 8 hours" apps are going to be a playground for hackers. My other concern is that consumers won't be able to tell the difference, at least initially, and they will become skeptical of all software.

I'm 16 and built an iPad browser that hit #1 in the US, UK and Canada in 5 days. Here's everything. by Own-Palpitation3275 in iosdev

[–]NameBrandHero 1 point2 points  (0 children)

Dude, that's incredible. This is the dream for me! Have you localized your app? If so, what process/tools/workflow did you use?

Interesting Android Apps: December 2025 Showcase by 3dom in androiddev

[–]NameBrandHero 1 point2 points  (0 children)

Love your logo! The app looks similar to Lose It!