Login

u/mheryerznka

r/iOSDevelopment r/Appstore r/founder r/appdev r/EntrepreneurRideAlong r/yerevan r/appledevelopers r/SaaSSolopreneurs r/AiAutomations r/AppBusiness r/QualityAssurance r/freelance_forhire r/micro_saas r/SaaS r/iosdev r/ClaudeCode r/Entrepreneurs r/buildinpublic r/highticket_sales r/SideProject
▲ 2 r/AiAutomations

Guys am I the only one that thinks lanchain is best way to go instead of n8n, make and other tools

Been building ML models, AI Agnets for about 6 years (tbh 5 years ML models and 1 year Agents ), including production systems for banks and US clients, and I keep landing in the same place. I always use LangChain for Agentic AI and honestly haven't even considered n8n or Make.

With code I get full control, real error handling, proper testing, and no lock-in. It also just holds up better.

So where do you all land on this? Am I the only one?

reddit.com
u/mheryerznka — 7 hours ago
▲ 10 r/AiAutomations

I want to find people who will introduce me as an AI guy

6 years in AI. currently working a 9-5 with US clients

now i want to build something of my own, an AI agency, and i'm not doing it to make a quick buck

the one thing i haven't cracked: getting my own clients. how did you get yours?

happy to do free calls if it turns into a referral

reddit.com
u/mheryerznka — 1 day ago
▲ 1 r/Entrepreneurs

Thank God It's Friday.

AI engineer here (6+ years, banks + US companies). i'm doing a AI  audits to
build case studies. i'll find where your team loses hours to manual work and show you what's
automatable plus rough time/$ saved. free, the only ask is i can document it (anonymized ok).
reply or DM with your most repetitive task. happy to share my linkedin as proof.
reddit.com
u/mheryerznka — 3 days ago
▲ 1 r/EntrepreneurRideAlong

Starting my automation agency in public — doing free audits to build my first case studies

i'm an AI engineer (6+ years, banks and US companies) starting an AI agency, and i'm doing it in the open

first step: i want real case studies, not made-up ones

so i'm doing a few free AI audits for your company/SaaS whatever

i'll map where your business loses hours to manual work and show you exactly what could be automated, with the time and money it'd save

free, no pitch. the only thing I want in return is that i can document the process (anonymized if you want) as i build this thing publicly

taking just a few, since i do each one myself

comment your business or your most annoying repetitive task and i'll reply. can share my linkedin as proof

reddit.com
u/mheryerznka — 3 days ago
▲ 3 r/AiAutomations

AI audit before doing AI Automation. Isn't that the approach?

Hey everyone,

I’ve realized that pitching a business with "Hey, I can build a chatbot for you" almost never works. Most non-tech founders and business owners don’t actually know what they need.

Because of this, I’m leaning heavily into doing a deep AI Audit / Discovery Phase before writing a single line of code or setting up a workflow.

For those of you doing B2B AI consulting or automation: How are you structuring this audit?

What frameworks are you using to diagnose their actual operational bottlenecks instead of just selling them a generic tool?

reddit.com
u/mheryerznka — 3 days ago
▲ 0 r/iOSDevelopment

Is an app store rejection actually a problem

been reading post after post lately on indie hacker and dev forums from people who spent months building tools for developers only to walk away with a handful of users. the consensus in the comments is always the same: if a dev doesn't have a tool, they'll just script it themselves, and they won't pay a solo founder for it.

if that's actually the ground truth, i think i need to pause my project for a week, breathe, and rethink the whole roadmap.

here’s the context. i’ve been building a pre-submission auditor for iOS builds.

The idea is that it scans your archive before you upload to app store connect and catches the exact issues that trigger automatic or manual rejections

I built it because dealing with app store rejections is a specific flavor of anxiety we all just collectively accept as a normal cost of doing business. i thought saving teams from wasted cycles was a sharp enough pain point to justify a paid tool. now i'm questioning that.

motivation has been tough lately. i recently processed my first couple of small payouts, which felt great, but scaling past that initial momentum into actual recurring revenue feels like hitting a brick wall.

so i'm asking the people who actually ship apps for a living, not theoretical advice.

My tool is testara.dev check it out

u/mheryerznka — 9 days ago
▲ 0 r/iosdev

Is an app store rejection actually a problem devs want solved, or do we just accept the pain?

been reading post after post lately on indie hacker and dev forums from people who spent months building tools for developers only to walk away with a handful of users. the consensus in the comments is always the same: if a dev doesn't have a tool, they'll just script it themselves, and they won't pay a solo founder for it.

if that's actually the ground truth, i think i need to pause my project for a week, breathe, and rethink the whole roadmap.

here’s the context. i’ve been building a pre-submission auditor for iOS builds. the idea is that it scans your archive before you upload to app store connect and catches the exact issues that trigger automatic or manual rejections—missing NS privacy strings in the info.plist, broken or placeholder metadata, guideline violations, or forgotten permission prompts. instead of just throwing basic linter warnings, it maps out exactly how to fix it so you can ship on the first try instead of burning a week waiting on app review.

i built it because dealing with app store rejections is a specific flavor of anxiety we all just collectively accept as a normal cost of doing business. i thought saving teams from wasted cycles was a sharp enough pain point to justify a paid tool. now i'm questioning that.

motivation has been tough lately. i recently processed my first couple of small payouts, which felt great, but scaling past that initial momentum into actual recurring revenue feels like hitting a brick wall.

honest feedback is appreciated, good or bad.

the project is testara.dev if you want to see the execution.

u/mheryerznka — 9 days ago
▲ 4 r/Appstore

app store rejections are bad, but am i just solving a problem devs won't pay to fix?

been reading post after post lately from founders who spent months building tools for developers only to walk away with a handful of users. and the same line keeps showing up in the comments: if a dev doesn't have a tool, they'll just build it themselves, and they won't pay you for it.

if that's actually true, i think i have to pause my platform for a week, breathe, and rethink the whole thing.

so here's what i'm building. it basically acts as a pre-submission auditor for iOS apps. it scans your build before you send it to apple and checks for the exact things that trigger rejections—missing privacy info plist strings, broken or placeholder metadata, guideline violations, or forgotten permission prompts. instead of just throwing generic warnings, it tells you exactly what to fix and how, so you can ship on the first try instead of waiting a week for a rejection letter.

i built it because app store rejections are one of those quiet, frustrating pains every iOS dev has felt, but everyone just eats the wasted days and moves on. i thought minimizing that pre-submission anxiety was a real enough problem to pay for. now i'm not so sure.

i'll be honest, motivation has been rough. i recently processed my first few tiny payouts just to keep going, but you can probably guess how hard it is to scale that initial momentum.

so i'm asking the people who've actually lived this, not theory:

  1. is the "devs won't pay" thing real, or is it more about finding the teams who value time over a weekend script?
  2. for anyone who built an iOS or dev tool, what actually got you your first 10 to 20 paying users?
  3. when you hit this exact wall, did pushing through pay off, or was pivoting/stepping back the smarter move?

appreciate any real talk, good or bad.

the tool is testara.dev if anyone wants to see what i mean.

u/mheryerznka — 9 days ago
▲ 1 r/highticket_sales

[Hiring] B2B Sales Partner. You prospect & close, I deliver. 20% or 5% MRR.

The bottleneck isn’t tech or delivery—it’s sales.

I’m an AI engineer with 6 years of experience building for US clients. I build production-ready Vertical AI Agents and automated systems for small businesses using FastAPI and Supabase. No brittle no-code wrappers or AI slop.

I handle 100% of the architecture, tech discovery, and delivery. I need someone to own the pipeline from cold outbound to signed contract.

The Split:

  • 20% of the setup fee on close.
  • If it monthly subscription you get 5%

You have: 3+ years in B2B SaaS, IT services, or agency sales, and you know how to pitch ROI/value to business owners instead of just selling "AI features."

I’ll equip you with deep case studies, video walkthroughs, and technical backing on sales calls when needed.

If you want a lean, long-term partnership with uncapped earning backed by an engineer who actually ships, hit my DMs with your sales background and how you like to hunt. Let’s get to work.

reddit.com
u/mheryerznka — 9 days ago
▲ 1 r/freelance_forhire

[Hiring] B2B Sales Partner. You prospect & close, I deliver. 20% or 5% MRR.

The bottleneck isn’t tech or delivery—it’s sales.

I’m an AI engineer with 6 years of experience building for US clients. I build production-ready Vertical AI Agents and automated systems for small businesses using FastAPI and Supabase. No brittle no-code wrappers or AI slop.

I handle 100% of the architecture, tech discovery, and delivery. I need someone to own the pipeline from cold outbound to signed contract.

The Split:

  • 20% of the setup fee on close.
  • If it monthly subscription you get 5%

You have: 3+ years in B2B SaaS, IT services, or agency sales, and you know how to pitch ROI/value to business owners instead of just selling "AI features."

I’ll equip you with deep case studies, video walkthroughs, and technical backing on sales calls when needed.

If you want a lean, long-term partnership with uncapped earning backed by an engineer who actually ships, hit my DMs with your sales background and how you like to hunt. Let’s get to work.

reddit.com
u/mheryerznka — 9 days ago
▲ 1 r/SaaS

Is building a dev tool as a first SaaS just a waste of time?

been reading post after post lately from founders who spent 2 to 4 months building something for developers and walked away with like 5 paid users. and the same line keeps showing up in the comments: if a dev doesn't have a tool, they'll just build it themselves. and even if they don't, they won't pay you for it.

if that's actually true, i think i have to pause my platform for a week, breathe, and rethink the whole thing.

so here's what i'm building. it scans your ios build before you submit to the app store, and checks for the things apple actually rejects apps over. missing privacy strings, broken or placeholder metadata, guideline violations, permission stuff you forgot, the usual landmines. instead of just throwing warnings at you, it tells you exactly what to fix and how. the whole point is you ship on the first try instead of getting rejected and resubmitting for the fourth time, losing a week each round.

i built it because app store rejections are one of those quiet pains every ios dev has felt, but everyone just eats the wasted days and moves on. i thought that was a real enough problem to pay for. now i'm not so sure.

i'll be honest, motivation has been rough. i recently started paying myself a little just to keep going. you can probably guess how long that lasted.

so i'm asking the people who've actually lived this, not theory:

is the "devs won't pay" thing real, or is it more about who you sell to and how you reach them?

for anyone who built a dev tool, what actually got you your first 10 to 20 paying users?

and the real question i'm stuck on: when you hit this exact wall, did pushing through pay off, or was stepping back the smarter move?

appreciate any real talk, good or bad.

the tool is testara.dev if anyone wants to see what i mean.

u/mheryerznka — 11 days ago
▲ 2 r/SaaS

Can I sell a SaaS without any users?

I have my SaaS and curious can I sell it without any users will anyone pay for it? Did you guys have an experience with it? How is it working?

reddit.com
u/mheryerznka — 11 days ago
▲ 11 r/SideProject

So I bought my own app for 13US. I was quite happy. Next time, it’ll be 10k. ))) Will it make me even happier,

I was losing my motivation, so I paid myself $13 from my own SaaS today.

A friend pitched in another $20 just to keep me from quitting.

Total revenue: $33.

It sounds minor, but after months of staring at server logs, debugging code, and building in a vacuum, seeing actual money move from my platform into the real world completely flipped a switch in my head.

Building in public is an isolating grind. Sometimes you just need a tangible reminder that the code you're writing is turning into a real, living business.

That $33 completely renewed my drive to keep pushing. Celebrated the tiny win, now it’s back to crushing bugs.

If you’re an iOS dev tired of getting burned by App Store rejections, I built this for us:https://testara.dev/

u/mheryerznka — 16 days ago
▲ 164 r/SaaSSolopreneurs+3 crossposts

My SaaS made its first $33. I paid myself $13 for motivation, and a friend pitched in $20 to keep me going. Honestly? It works.

Hey everyone,

I wanted to share a small but incredibly motivating milestone with the community today.

After months of development, I officially processed a $13 payout from my SaaS platform into my bank account. To add to the momentum, a close friend pitched in another $20 purely as a motivational gesture to keep me pushing forward.

Total revenue: $33.

It sounds minor, but after spending months locked in a room staring at server logs, reading Apple developer guidelines, and debugging code, seeing actual money move from the platform to the real world completely changes your mindset. It’s a tangible reminder that the project is alive and out of the "local dev" vacuum.

The app is https://testara.dev/

What the project is about: If you’ve ever shipped an iOS app, you know the absolute nightmare that is the App Store Review process. Your app can work flawlessly on your machine, but then you submit it and get hit with a vague rejection because of a missing Privacy Manifest, an unclear subscription terms string, or a missing NSLocationWhenInUseUsageDescription in your Info.plist.

Every rejection costs engineering time, delays your launch, and chips away at team morale.

I built Testara to completely kill this pre-submission anxiety. It essentially acts as a pre-audit before Apple even sees your build.

Data-handling-wise, it’s built to be secure: it extracts the signals on the simulator, generates the report, and immediately deletes the original file. No long-term build storage.

Getting the analyzer to accurately map code signals to Apple's moving target of guidelines was a massive engineering puzzle, but the platform is finally live.

Shipping as a solo creator can be an isolating grind, and celebrating these small, early milestones—even a $33 start—is exactly what you need to stay driven for the next phase.

If you’re an iOS developer or lead a mobile team, I’d love to get your feedback on the tool. You can run one full audit for free every two weeks to test it out. Check it out at https://testara.dev/

I’ll be in the comments if anyone wants to chat about handling privacy manifests, iOS build analysis, or how I plan to spend my $13!

u/mheryerznka — 17 days ago
▲ 2 r/buildinpublic

Building an AI Agent to kill the App Store rejection loop. I need distribution advice!

Hey r/buildinpublic,

Apple rejects nearly 2 million app submissions every year. To fix this, I am building an Autonomous AI Agent for iOS App Store Compliance Validation. It unpacks compiled binaries locally to catch structural issues, checks metadata against the latest guidelines using AI, and proposes exact code fixes.

I know distribution is king, so I need help with my go to market strategy for two distinct audiences:

  1. Indie Devs and Vibe Coders: They often lack compliance literacy and only look for tools after getting rejected. My plan is a $6 pay per scan model. How do I organically reach them before they submit without burning cash on expensive ads?
  2. Enterprise and Agencies: For larger teams, this is a premium monthly subscription that acts as insurance against costly launch delays. How do you approach B2B sales for an automated pipeline integration tool? Do I target product managers or QA testers?

Any brutally honest feedback on the idea or how to build a distribution engine would be amazing!

reddit.com
u/mheryerznka — 1 month ago
▲ 3 r/appledevelopers

How are you guys dealing with App Store reviews and avoiding rejections?

Hey everyone,

I have been reading about developers getting stuck in the reviewing loop, getting rejected anywhere from 3 to 20 times before finally getting approved. It seems like a lot of people are getting hit with 4.3(a) design spam rejections.

From what I gather, reviewers only spend about 90 seconds looking at an app. If your best features need days of data to populate or sit behind a paywall, they just see an empty template and reject it.

I have seen some great advice for getting approved, such as:

  1. Preloading demo data with historical records so the app looks alive on the first launch.
  2. Unlocking premium features for the review build.
  3. Leaving detailed reviewer notes that clearly explain what makes the app unique.
  4. Scheduling a phone call with an Apple representative to explain standout features.

What other strategies are you guys using to get through the review process? Have you found any specific onboarding changes or communication tactics that work best to avoid getting rejected? Would love to hear your experiences!

reddit.com
u/mheryerznka — 1 month ago
▲ 1 r/AppBusiness

How much time have App Store rejections actually cost you?

I'm particularly curious about:

  • Common rejection reasons
  • Things that waste the most time during review
  • What parts of compliance or submission feel the most manual and annoying

Would love to hear some real stories from people who've been through it.

reddit.com
u/mheryerznka — 1 month ago
▲ 1 r/founder

I’ve been heads-down on Testara (testara.dev) for months.

The tech works. The agents are fast. The landing page looks "startup-y" enough. But I realized I’ve been playing a dangerous game: Validation via Waitlist.

I have names on a list. Names are easy. Credit cards are hard.

I’m tired of guessing if this is a "must-have" or just a "cool-to-see." So, I’m making a rule for myself before I ship the next update:

The $50 Validation Gate.

I’m asking for 5 beta users to put down a 100% refundable deposit.

  • If they don't like the tool? Refunded.
  • If I don't ship? Refunded.
  • If they love it? It goes toward their first month.

It’s the most uncomfortable thing I’ve done as a dev. But if I can’t find 5 people who care enough to risk a temporary $50, I don’t have a business—I have a hobby.

reddit.com
u/mheryerznka — 2 months ago
▲ 1 r/QualityAssurance

Is anyone else starting to feel like scripted regression testing is just a "security theater" for mobile?

Don't get me wrong it’s great to know the Login button still works. But it feels like 90% of our actual production "fire drills" come from things no script would ever catch:

  • The State Chaos: A user starts an upload, gets a phone call, the app goes to background, they lose signal, and then they try to resume the upload after the OS has partially purged the app’s memory.
  • The Hardware Weirdness: Thermal throttling kicking in on an older device and causing a race condition in a UI animation that works perfectly on a high-end simulator.
  • The "User Logic": A user tapping a button four times while a network request is hanging, bypassing a state guard because it wasn't designed for "jittery" interactions.

I feel like we’re getting really good at testing the "Happy Path" and even the "Sad Path," but we’re completely blind to the "Chaotic Path."

Short of hiring a room full of people to just "break things" for 8 hours a day (the dream, but expensive), how are you all handling this? Are you relying on monkey testing, sophisticated error monitoring (Sentry, etc.), or just crossing your fingers and waiting for the App Store reviews?

reddit.com
u/mheryerznka — 2 months ago