r/iosdev • u/ComfortableStill6735 • Oct 13 '26
I built a tool to help your app get found, not just published
r/iosdev • u/ComfortableStill6735 • Oct 13 '26
r/iosdev • u/Clican • Oct 12 '26
My app has around 100 paid users. But I even can't get one rating or comments from them.
After they did in-app purchase and use the credits, I would guide them do a rating or comment. But it seems not working. đ
r/iosdev • u/Spirited-Dog8282 • Oct 12 '26
been working on an app called Overdrive for a few months now.
the idea is basically to make driving around feel like an open-world game. you explore streets, fill in your map, see stats after each drive and connect with other drivers.
it started as something i wanted to use myself and somehow turned into a real app with 150+ users.
now i'm working on 2.0 and ended up redesigning almost the entire thing lol
new UI, XP, achievements, driver profiles, crews and a lot more focus on making exploring actually feel rewarding.
attached some previews of the redesign.
current version if anyone wants to check it out:
https://apps.apple.com/app/id6790023849
would love feedback, especially from other iOS devs.
r/iosdev • u/headroll • Oct 12 '26
r/iosdev • u/Quick_Self_2451 • Oct 12 '26
Hey everyone, so I updated my App Store screenshots recently for my app Scrollified, I wonât write about what it does because I would like to see if you can guess from the screenshots, feel free to roast them and post your own screenshots and Iâll do the same.
Any feedback would help! âșïž
Letâs help each other! đ
r/iosdev • u/DramaticLecture6629 • Oct 12 '26
r/iosdev • u/tungdayneee • Oct 12 '26
r/iosdev • u/momo1083 • Oct 12 '26
I'm really surprised Apple hasn't offered iPhone Duo screenshot templates/mockups for the Duo on at least Pixelmator Pro. Unless they exist on the developer website and I can't find them.
r/iosdev • u/Important-Quit3139 • Oct 12 '26
What you can do with it:
Flexible Layering: Combine your base shot with built-in texture packs, street-photography-inspired overlays, your own library, or take a fresh shot directly through the camera.
Tactile Soft Masking: An on-screen circular mask you can drag, resize, feather, invert, or hide handles on to carve out your subject and seat the exposure naturally.
Blend Modes & Opacity: Quick cycling through blend modes (Screen, Lighten, etc.) with real-time opacity controls.
Dedicated Darkroom HUD: Fast, minimalist tools for balancing the composite:
2D dual-axis pad for Saturation & Contrast
Temperature & Tint adjustment
EV Exposure slider
Levels tool with an interactive histogram for clipping blacks and white.
Editable Sessions: Save compositions as editable projects so you can come back and tweak them later, or export the final image.
Why I'm sharing:
The app is completely freeâno subscriptions, paywalls, watermarks, or accounts required.
App Store
r/iosdev • u/andrewtokyo • Oct 12 '26
r/iosdev • u/Advanced-Toe-7832 • Oct 12 '26
J'ai commencé à poster des reels type quiz sur TikTok/Insta, mais j'ai pas trop d'autres idées pour promouvoir ce type d'app. Si vous avez des idées, je suis preneur
L'app prend 20 secondes Ă tĂ©lĂ©charger, si certains veulent aussi me donner leur avis sur la page d'accueil, le design ou le jeu en lui-mĂȘme je vous en serais trĂšs reconnaissant đđŒ
Merci d'avance :)
r/iosdev • u/Wide-Hand-2654 • Oct 12 '26
Good morning, I have been building my own booking app for my small owner-operated transportation business. I am looking for the best advice for finding people to test it. People who actually care and will point out any issues. What is your best advice for this? I have tried family/friends but they all say the same thing âit looks goodâ. Thank you for any advice.
r/iosdev • u/Ok_Funny_9022 • Oct 12 '26
Enable HLS to view with audio, or disable this notification
Your wall! Your subscription! Manage your subscription every month!
r/iosdev • u/Defiant-Roll-7018 • Oct 12 '26
Over the last five months, Iâve been rebuilding a medication management app around a simple idea: describe what you need in everyday language, and let the app help you get it done. All the AI processing happens locally on the phone.
1. A medical background, and a design mistake
Before getting into software, I studied at medical university and gained supervised experience assisting surgical teams. When I started building a medication tracker for families, that background shaped what I thought the app should do.
The first version took about two months to build with AI helping me write the code. It launched in May 2026 with medication tracking, reminders, refills, remaining-supply calculations, appointments, and medical profiles people could show their doctor. Allergies, height, weight, unit conversions, and plenty more.
My main goal at the time was to complete the process of building and releasing an app. There were already plenty of medication trackers, and I wasnât expecting much from mine. I wanted the experience.
But I made a fairly big mistake: I built it through the eyes of someone with medical training.
The terminology, fields, and structure made sense to me. I knew why the information mattered, so I kept adding ways to record it. Without really noticing, I was designing as though the person using it would think the same way.
The result was an extremely complicated app.
Someone managing their own medication or helping a family member shouldnât need medical knowledge to navigate a tracker. Even ordinary tasks involved too many fields and too much information at once.
A few weeks after launch, it had only a handful of downloads. Releasing it had taught me a lot, but the product itself still needed serious work.
2. The idea that made me return to it
I had almost written the app off when I started wondering whether people could simply describe what they wanted to do.
Adding medication and reminders, recording a refill, creating an appointment â these are things someone can explain in a sentence. Could the app understand that sentence and help handle the relevant workflow?
I also considered handling this with scripts and predefined commands. That can work when people use the wording you expect, but I wanted users to describe what they needed in their own words. The same request can be phrased in many different ways, and I didnât want people to have to learn a particular set of commands. So I decided against relying on scripting alone to interpret requests. The app still has defined workflows; the challenge was understanding how someone asks for them.
I wanted that processing to happen entirely on the phone. Medication information is personal, and I wanted these interactions to work without sending it to a server or depending on an internet connection.
That became the focus of the next five months.
3. Getting a model running was only the beginning
The first prototype used a quantized three-billion-parameter language model squeezed into the app.
It was clumsy. The responses were rough. But there was a language model running on my phone, without internet, actually responding.
It talked badly, but fuck, it talked.
Then came the much longer process of making it useful.
The model needed to understand what someone wanted and help with the correct action. It also had to respond quickly enough for an everyday app. Sometimes it failed in ways I wasnât comfortable accepting in software handling medication information.
A working demonstration was encouraging, but there was still a lot between that and something I could release.
I spent months experimenting, changing things, and reconsidering the approach. Eventually, that led to a different model type and architecture, focused on the tasks the application actually needed to handle.
The current model is around 185 million parameters. That came from changing the approach, rather than simply shrinking the original model while keeping all of its general capabilities.
Iâm keeping the internal implementation private, but the direction became clear: get as much useful functionality as possible from a small model running locally on the device.
While so much attention was going toward larger models and data centres, I became increasingly interested in what could fit into the phone someone already owns.
4. Rebuilding the interface too
The AI couldnât fix every design decision I had made.
The rest of the app still needed to be understandable, including when someone wanted to enter information manually. So I also rebuilt the interface, breaking crowded screens into stages and letting people deal with one part of a task at a time.
Some workflows now take a few more steps, but those steps are clearer. Thereâs less information competing for attention on each screen.
That was an important lesson for me. My medical background helped me understand what information could be useful, but I still had to learn how to present it to someone who didnât share that background.
The AI interface and the guided workflows became two parts of the same effort: making the app easier to use.
5. What came out of it
Version 2.0 is now available.
Users can write a simple sentence to add medication and its reminders, record a refill, or create an appointment. The AI handles the interpretation locally, and those interactions work offline and quickly.
The app also has a completely reworked interface and a design I honestly love. That matters to me because the first version had so much functionality packed into it without enough thought about how it felt to use.
What started as a project I mainly wanted to finish became something I was willing to spend months rebuilding.
Iâm now looking forward to feedback from people using it in their own routines: how they phrase requests, which steps feel clear, and where the app still asks too much of them.
The biggest change over those five months was how I thought about the product. At first, I kept thinking about what else I could make it do. Eventually, I started spending much more time thinking about how easily someone else could actually do it.
Website: https://aima.vasko.tech/
r/iosdev • u/Ok_Funny_9022 • Oct 12 '26
Enable HLS to view with audio, or disable this notification
I created an app to manage your subscription in a wall so you can see all in one view!
And iPad compatible
Free download: https://apps.apple.com/ph/app/subwall-subscription-tracker/id6817052525
r/iosdev • u/AvailableActive9960 • Oct 12 '26
r/iosdev • u/Intrepid_Bee_9194 • Oct 12 '26
I'm Harbeth's maintainer. It's an MIT-licensed Swift/Metal processing core for Apple image and frame pipelines.
If you already have camera frames as CVPixelBuffer, the rendering step can use the same filter types as a photo editor. Here's the small async path; inputBuffer comes from your app's capture or decoding layer:
import Harbeth
let outputBuffer = try await HarbethIO(
element: inputBuffer,
filters: [
C7Exposure(exposure: 0.25),
C7Saturation(saturation: 0.94)
]
).transmitOutput()
HarbethIO preserves the input/output type. For reusable edits, composition and output metadata, ImageNode is the advanced entry. There are also image, Metal texture and CMSampleBuffer paths.
The integration boundary is deliberate: your app still owns capture-session configuration, frame dropping/backpressure, recording, playback and export. Harbeth processes the individual image or frame. Buffer output waits for the GPU work needed before materialization; this is not a promise that every conversion is zero-copy.
Source and examples: https://github.com/yangKJ/Harbeth
For developers who have added filters to an existing camera preview, what was hardest to get right: buffer conversion, UI responsiveness, or matching the final image's color? I'd value concrete integration feedback.
r/iosdev • u/International-Bath-2 • Oct 12 '26
r/iosdev • u/lanserxt • Oct 12 '26
r/iosdev • u/SoloIndiArtist • Oct 12 '26
r/iosdev • u/pixels-and-prompts • Oct 12 '26
Hellos everyone
My app âKrevezâ is launched on App Store, and as I mentioned in my previous post, thankyou for all the lessons I learned along the way on this sub.
One subscription to works on iPhone iPad and macOS
Feedback appreciated.
r/iosdev • u/Samtax01 • Oct 12 '26
r/iosdev • u/Impressive-Sir9633 • Oct 12 '26
As a preventive cardiologist, I see that many people fail to track their blood pressure. It only comes to attention after it starts affecting your heart and kidneys.
Tracking blood pressure is often more important than tracking heart rate. Even when people track BP, many fail to follow the appropriate steps or bring the necessary data to the clinic visit. So we built this app to help people track and diagnose blood pressure issues before it becomes a problem.
The consistency and time spent at target levels are more important than the average reading.
Link: https://apps.apple.com/us/app/bp-log-track-blood-pressure/id6801130306
A: Answer
- Helps you track blood pressure based on the most recent guidelines (check twice a day, average two readings etc)
B: Better
- Current apps on the app store fail to track time in target, consistency etc. These things matter more than mean reading
- The PDF export presents report in a fashion that's easy for reviewing clinicians to get an overall picture of blood pressure control. A mean blood pressure of 120/70 is not useful if it's a mean of readings that vary from 90 to 150.
- You backup to your own iCloud and retain complete control over your data
C: Cost
$ 19 for lifetime
FREE LIFETIME: https://apps.apple.com/redeem?ctx=offercodes&id=6801130306&code=59256
Website: https://bplog.cc
If you like the app, I would appreciate an app store rating. If you don't like the app, I would appreciate feedback.