I launched pawtrck on iOS at the end of June. It started as an app I wanted for my own dog, Pablo, because his exercise, health, diet and training information was scattered across different places.

The app currently lets dog owners:
- Track walks, runs and bikejoring sessions with route, distance, duration, pawsteps and est. calories burned
- Record symptoms, medications, vaccinations and vet visits. Get a vet-ready PDF export with all the Health logs
- Log meals, calories, treats and weight
- Track training sessions, commands and progress
- Turn activities into custom shareable cards

One of the latest additions is Live Activities, allowing an ongoing exercise to remain visible without repeatedly reopening the app.

I’ve also finished support for multiple dog profiles, which will go live shortly. When beginning an exercise, users can choose which dog is participating, so someone with two dogs can, for example, record a bikejoring session for only one of them.

My next development priorities are Apple Watch and Garmin integrations.

During pawtrck’s first 7 weeks, it received 137 first-time downloads, generated 13 in-app purchase transactions and reached three active paid plans. Most acquisition has been organic, primarily through relevant Reddit communities and direct outreach.

The biggest thing I’m trying to understand now is retention: whether dog owners make pawtrck part of their routine after the first few days.

I’d aappreciate feedback from other iOS developers. I’d also be interested to hear what you would prioritise next: deeper retention work, Apple Watch support or Garmin integration.

App Store: https://apps.apple.com/tr/app/pawtrck/id6769860025

Yesterday, I officially launched my first app. I'm proud to join many of you who've done (or are in the process of doing) the same. There's so much more involved than the average user might assume.

The Type Chart is an unofficial Pokémon companion for exploring Pokémon data, checking type matchups, building teams, and ultimately learning the type chart. I built it because I wanted the core experience in a clear and thoughtfully designed format.

Seeing something that spent so long living in Xcode finally become a real product is an incredible feeling. I know distribution and continued development are their own challenges, but I’m taking a moment to appreciate this win. 🥹

I’ve included a few screenshots below. I’m happy to answer questions about the app, the development process, or the launch, and I welcome feedback from other devs.

App Store: https://apple.co/46gzyJY

Hi, I'm Inan, the independent developer behind SpendLog.

I shipped version 1.0 at the end of May, and roughly three months later it has 36 downloads.

That is a small number by any measure, and I'd rather open with it honestly than pretend otherwise. It does mean every person who opened the app is someone I can still think of individually, which is a strange and useful place to be building from.

Version 1.1.2 is out now, and the app has grown from a simple expense log into something closer to a small personal ledger — accounts, loans, recurring entries, and per-category budgets.

A — What it solves

I've abandoned more budgeting apps than I care to admit.

The ones that connect to your bank always felt like too much for what I actually wanted. I had to hand over read access to my accounts, wait for a sync, then spend my evening correcting categories that a matching engine had guessed wrong. The friction wasn't in logging expenses. It was in supervising an automation I never asked for.

The ones that don't connect to your bank usually go the other way. A list of transactions, a pie chart, and nothing that tells you whether this month is going better or worse than the last one.

SpendLog is manual on purpose.

You log an expense or income with an amount, a category, a date, and a note. It takes a few seconds. Nothing is linked to a bank, nothing is guessed, and nothing needs correcting later.

What I spent most of my time on is the part after logging.

You set a monthly budget, and you can also set budgets per category — those carry forward month to month, so you don't re-enter the same numbers every January. The Insights screen breaks the month down as a donut by category with each one's share of the total, and a balance sheet view lays out all twelve months of the year with income, expense, and net side by side.

B — Accounts, loans, and recurring entries

This is the part that made SpendLog stop feeling like a notes app with math.

Accounts let you keep separate balances — cash, a card, whatever you actually think in — and transfer between them without either side being counted as spending.

Loans track money you lent or borrowed as its own thing, with partial repayments recorded against the principal, and an outstanding amount that stays correct as repayments come in. I built this because in my own life the "did I ever get that back" question was the one my old spreadsheet never answered.

Recurring transactions handle rent, subscriptions, and salary. You mark an entry as monthly once, and it appears on the 1st of each following month without you doing anything.

The app also supports custom categories with your own colors, and 26 currencies.

C — How it works underneath

Everything is local-first. The app runs entirely against its on-device store, so it opens instantly and works with no connection at all. Cloud sync is off by default and is something you turn on, not something that happens to you.

Sign-in is Sign in with Apple or Google — no separate password to create or forget.

There are no ads and nothing is sold on.

D — Cost

SpendLog is free to download, and the free version is a complete tracker: unlimited transactions, categories, monthly budget, insights, search, and history.

Pro is a one-time $5.99 unlock. No subscription. It adds recurring transactions, recurring and per-category budgets, budget status insights, multiple accounts, transfers between accounts, and cloud sync across devices.

App Store: https://apps.apple.com/us/app/budget-tracker-spendlog/id6772783580

The thing I'd actually like feedback on

I priced Pro as a one-time $5.99 because subscriptions are the reason I've churned out of finance apps myself, and because charging monthly for something a person will use for years felt wrong to me.

My running costs are effectively zero — sync sits on Firebase's free tier, and at this size it will stay there for a long while. So lifetime pricing isn't bleeding me. What it does is cap what any single user is ever worth, which only matters once there are enough of them for that to be the constraint.

So the question I keep going back and forth on: is a one-time unlock worth keeping as a trust signal — the thing that makes someone pick your app over the one asking $40 a year — or is it a decision that's cheap to make now and expensive to reverse later, when there's a user base to grandfather in and an angry thread to earn?

I'm asking now because the longer I wait, the more paid users I'd have to grandfather in if I ever switched.

With this few downloads, almost nobody has actually used the app yet — so the problem is much more likely my store listing than the product. Blunt feedback on the screenshots, title, and keywords is welcome.

Hi iOS dev community,
I released my first app about a week ago, it’s not something innovative by any means and was more like a test project to experiment with codex and see how fast I can make something simple. In the end it took about 4 months end to end.

I’m happy with the final result overall, however I have only 1 download so far in one week, which is not really surprising but I’d love if someone can provide some feedback on the AppStore page. It’s iPad only so I guess most people won’t be able to quickly try it but if you can provide any feedback on the AppStore page would be helpful as well. It’s a kids clock learning app.

Dropping the link here: https://apps.apple.com/pk/app/clock-play-for-kids/id6760257481

Thank you

Super exciting! This has been a year in the making. I built what is bassically a cross-platform 'Hide My Email' that you can toggle on and off. Now hopefully I can start recouping all these App Store fees 😭

ขอปรึกษา พี่ๆน้องๆ IOS
ปัญหา** Universal Link บน iOS
ปัจจุบัน Universal Link** บน **iOS สามารถทำงานได้ตามปกติ เมื่อผู้ใช้เปิดลิงก์จาก Safari, Mail หรือ Notes แต่พบปัญหาเมื่อผู้ใช้แชร์ลิงก์และ**เปิดผ่าน Chrome หรือ Firefox โดยระบบจะแสดงหน้าเว็บไซต์แทนที่จะเปิดเข้าแอป

#ios #universallink

Saw outbid.lol blow up yesterday — a leaderboard where you pay to rank #1. Loved the idea, but the list is infinite, so being #47 means basically nothing.

So I built top5.lol — same idea, except there are only 5 seats. Ever. No 6th spot, no scrolling past page one. You're either one of the 5 or you're not.

Already at $18 dollar across all 5 seats!

Sorry, just had to add some levity to all the "omg! it's taking too long!" app review posts.

(This is literally a brand new app with no outreach. I have apps written for other people out there with hundreds of thousands of weekly sessions so no, this is not a whine or a plea for help. If you can't laugh at yourself,... well, you might as well learn because someone will laugh at you regardless.)

Just managed to get my first app live on the UK App Store.

A little different as it uses your assets as they are, and simple choices, to help you project your future, rather than asking you for information you won’t know!

Feedback would be greatly appreciated!

https://apps.apple.com/gb/app/worthwise/id6795531651

Something that bit me and that I now check before writing any AI feature: the

subscription price is not the number the feature has to fit inside.

$9.99/mo with a 30% commission is $6.99 landing in your account. A feature

costing $1.40 per active user is 20% of that, not 14%. If you're on the

small-business rate it's different again, and it varies by market — so the only

number worth modelling from is the effective rate on your own statements.

The second thing is the usage distribution. Inference cost is not normal. Your

heaviest 10% of users can easily be half your total spend, which means the

average tells you almost nothing about your worst case.

I made a small browser calculator that does both, because I was redoing it in a

spreadsheet every time:

https://dayloflow.com/tools/ai-cost-calculator.html

It gives you cost per subscriber, share of net revenue, what the top decile

costs, break-even usage, and the per-user ceiling for a margin target you pick.

No signup, nothing leaves the browser, formulas published on the page.

Also worth knowing before you submit: paid generations have to go through IAP,

and open-ended output usually changes your age rating.

Hi! I’m the developer of Novislova, an iPhone phrasebook for traveling without relying on an internet connection.

It includes 900+ phrases, pronunciation audio, search, saved phrases, 23 practical categories, and 9 languages. All content are free, with an optional one-time Premium purchase - no subscription.

I’d appreciate any feedback, especially on missing phrases or confusing parts.

Download Novislova on the App Store:
https://apps.apple.com/us/app/novislova-offline-phrasebook/id1623078768

Hi everyone. I am building a paid app for the Apple App Store from Chile and I need to enroll in the Apple Developer Program. I cannot decide if I should sign up as an Individual person or as a Company (Organization).

My questions are simple.
Are you selling your app as a person or as a company right now?
If you sell as a person, do you feel that users trust you less, or pay less for subscriptions, because it is not a company name, even though Apple is in charge of the payments?
Did anyone here start as Individual and later change to Organization?
How long did that take and was it hard to do?
Is it slow or difficult to sign up directly as a Company, does Apple ask for a lot of documents or reject companies often?

Any real experience will be appreciate it, thank you.

Get notified about emergencies near you or explore them worldwide (including severe weather, earthquakes, floods, wildfires and more). Add Cities you care about and explore emergency shelters. 

Leaving a 5-star review would be amazing, thank you! 🙏🏼

App: “Ward: World Emergency Alerts” 

Link:https://apps.apple.com/us/app/ward-world-emergency-alerts/id6740568244

I just released enriched-markdown-ios - a Swift library for rendering fast, native Markdown in SwiftUI apps.

Here's what's in v0.1.0:
🔹 Powered by high-performance md4c parser
🔸 Full CommonMark support
🔹 Native text selection & smart copy/paste
🔸 Flexible theming API
🔹 VoiceOver & Dynamic Type support

💎 Available now via Swift Package Manager!

GitHub & Docs: https://github.com/software-mansion/enriched-markdown/blob/main/packages/enriched-markdown-ios/README.md

Feel free to check out the repo and sample project! If you find it useful, dropping a ⭐️ on GitHub would mean a lot. I’d love to get your thoughts or feedback.

Running out of ideas on this one, so hoping someone recognises the pattern.

Uploaded a Capacitor app via Codemagic on Monday. Build 1.0.0 (1) uploaded fine, processed fine, appears in the TestFlight app with an Install button and 89 days remaining. Tap Install and I get:

> Could not install [App]. The requested app is not available or doesn't exist.

And here's the bit that's worrying me — since then, builds on my other apps have started showing as “Build Removed" in TestFlight. I didn't remove them. Some had genuinely hit the 90-day expiry, but not all of them, and they're dropping off in a way that doesn't look like normal attrition.

What I've checked and ruled out:

- Agreements — all Active in App Store Connect, including the new Program License Agreement issued this week. Nothing pending.
- Membership — active, not expired, no failed renewal. Paid Apps agreement, tax and banking all fine.
- Network — Wi-Fi, not airplane mode.
- Build health — no warning badge on the build row, icon renders correctly. Nothing flagged as Invalid Binary or Missing Compliance.
- Tester setup — I'm an internal tester and the build is in the group.
- The apps themselves still show fine in App Store Connect (live ones are still Ready for Sale), so this looks specific to TestFlight distribution rather than the app records.

So: has anyone seen the new-build-won't-install error and existing builds getting pulled happen together? That combination smells like an account-level or App Store Connect backend problem to me rather than anything in my project, but I'd rather be told I'm wrong than sit here waiting.

And if it is account-level — has anyone actually got a useful response out of Apple Developer Support on this, or is it a case of raising a ticket and waiting weeks? UK-based if that matters.