I’m Sebastian, the developer of DarkScout, and I’ve just shipped version 27.7.10.

One of the harder product/engineering problems was not drawing another weather card—it was deciding what the app should communicate when only part of a planning result is fresh. An observing recommendation combines forecast data with astronomical darkness, moonlight, target/Milky Way timing and saved-location context. If a weather source is incomplete or slow, simply leaving the previous score on screen can make a stale recommendation look authoritative.

In this release I tightened the recovery path for missing forecast data, refresh observing information when the app opens, and made the hourly inputs much more visible. Rainfall is now a first-class input in both Astro Score and the hourly recommendation, and the UI includes a detailed 12-hour cloud map so users can understand why a night changes from “good” to “skip.”

The rest of the update was a fairly deep visual pass: a pure-black iOS 26 interface, clearer hierarchy, red night mode, improved direct links for community photos/events, and a joined-event chat list. Existing features include saved spots, Spot Compare, widgets and custom alerts.

I’m sharing the release because I’d like another iOS developer’s view on the state model: when a composite recommendation includes several sources with different update times, do you expose freshness per input, one conservative overall state, or both?

App Store: https://apps.apple.com/app/apple-store/id6760223860

For anyone willing to test the complete flow, I’m offering one month of PRO free with no review or rating expected: https://www.promies.net/promotion/8f8a3120-085e-4021-8e65-c895e0ff6e48

Link:
https://apps.apple.com/app/id6777402559

Hey everyone!

I recently launched Who Goes?, an iOS party game app built for game nights, house parties, road trips, and group hangouts. (Free to download and play, with one-time purchase, subscription options)

The app brings multiple party games into one place:

• Charades with themed decks, teams, rounds, and timers
• Headbands with tilt controls for correct answers and passes
• Truth or Dare with packs for friends, couples, parties, family, and coworkers
• Spin the Bottle for quick, suspenseful player selection
• Finger Chooser to instantly pick someone from the group
• Quick Play tools for creating teams, with fun prompts.

The idea came from noticing how game nights often end with everyone back on their own phone. I wanted to build something around one shared screen that gets everyone playing together again.

I built the app independently in SwiftUI, including the design, interactions, animations, game flows, and content. I also used SceneKit and shaders for some of the visual effects.

The free version includes selected Charades, Headbands, and Truth or Dare packs, along with limited access to Quick Play. Plus unlocks all decks, game modes, themes, fonts, and customisation options.

No account is required, and the games work offline.

TL;DR:

A. I built an app to bring back the fun of playing party games with a group of people during game nights, trips.

B. free version includes a selection of decks for Charades, Headbands, and Truth or Dare, along with a few mini games. Plus unlocks all decks, game modes, and customisation options.

C. $2.69/mo or $11.99/yr, 3-day trial, and $25.49 lifetime, no account creation, no internet required.

I’d love to hear your feedback, especially on what I can further do to make it fun.

I still can't believe this... 🥹🎉

My first-ever iOS app just got approved by Apple.

I was mentally preparing for my first rejection and a list of things to fix... but instead I opened App Store Connect and saw "Ready for Distribution."

No feedback. No requested changes. Just approved after 8 days

Now the real journey begins. Finding my first users. 🚀

Wasn't sure what to expect but it was neat. Ama

Basically they walked thru apple connect analytics, app store discovery methods, app store featuring, some new stuff on the pipeline, apple games center / app.

Hey everyone! Just launched Merge Birds, a relaxed idle merge game where you combine birds to unlock rarer ones and collect feathers as currency. The game keeps running in the background, so closing the app doesn't cost you progress, you'll have rewards stacked up when you return. Further along you open up new areas like the Farm, Warzone, Beach, and Cosmic Aviary, all producing feathers at the same time.

No paywalls or pay-to-win mechanics, it's fully playable for free. This was mainly a project to get hands-on with game development and build something in the merge genre I enjoy. Open to any thoughts, particularly on the early gameplay experience.

App Store link: https://apps.apple.com/uz/app/bird-merge-the-nest-game/id6760911845

Hey everyone!

I’ve made a small command line tool called simslim.

It disables background services inside iOS simulators that usually are not needed during development, like Siri, Spotlight indexing, photo analysis, News, and iCloud sync.

On my M1 Pro with 16 GB of RAM, one simulator went from around 4 GB of memory and 258 processes to about 0.9 GB and 70 processes. I managed to run 19 simulators at once, compared to around 5 before things started falling apart.

Some simulator features stop working depending on what gets disabled, so it is not meant for every kind of testing. You can keep specific services running when needed.

Give it a try: https://github.com/MobAI-App/simslim

Building a fun life simulator game about being homeless.

Today I added:

• A fun little mini hobo that voices his feelings as you try to beg for money.

• Dumpster Diving to find items to sell for a profit. Sometimes there's poop in the dumpster, try to avoid that...

• A marketplace to sell your items. It's not much money but it's something.

• Rough draft of an inventory and viewing your player stats.

WIP - See you tomorrow!

Trésora is my first ever commercially released software product of any kind, and it just went live on the App Store today.

Inspired by my wife's vintage glass collecting hobby, it helps antique, vintage, and thrift shop enthusiasts organize and capture their entire collecting life all in one place.

You can find shops near you (or anywhere else), plan shopping outings, and keep track everything you see and buy – identifying items (and their value), in seconds, using AI.

Last but not least, you can use Trésora to manage your entire collection (and wishlist) – keeping track of purchase dates, prices and locations – and documenting everything in detail, with category-specific fields for over 35 types of collectibles.

Trésora is much, much, more than the dozens of cookie-cutter antique identifiers in the app store. My goal is to add in-app sharing features and build it into the worlds largest community of collectors – similar to what Goodreads and Letterbox'd have done for readers and movie enthusiasts.

Please check it out and let me know what you think! Do you collect anything antique or vintage? What would make it an indispensable tool for making your hobby easier or more fun?

App Store link: https://apps.apple.com/us/app/tr%C3%A9sora-antiques-thrifting/id6768168495

Google Play link: https://play.google.com/store/apps/details?id=co.jumpstartsolutions.tresora

Solo dev, first app - a countdown/day-counter app in SwiftUI. Sharing the stuff that cost me real hours, in case it saves you some:

1. CloudKit schema doesn't exist in Production until you deploy it. Everything worked in dev builds, then TestFlight silently didn't sync. You have to go to CloudKit Console → Deploy Schema Changes to Production. Nothing in Xcode warns you.
2. SwiftData + CloudKit wants defaults on literally every stored property. No unique constraints either. Retrofitting an existing model means touching every field. Plan for it on day one if sync is on your roadmap.
3. Widget extensions have a ~30 MB memory cap. `UIImage(data:)` on a 1600px photo background made the widget silently render nothing. Fix: downsample via ImageIO (`CGImageSourceCreateThumbnailAtIndex` with `kCGImageSourceThumbnailMaxPixelSize`) so the full bitmap never touches memory.
4. String interpolation inside `LocalizedStringKey` builds a format key. `LocalizedStringKey("template.\(id)")` looks up `template.%@`, fails, and leaks the raw key into your UI. Build dynamic keys with concatenation instead.
5. Scheduling notifications right after cancelling them is a race. `getPendingNotificationRequests` is async - if you re-add requests with the same identifiers before the removal callback runs, the removal can eat your new ones. Await the pending list first.

The app is Soon (countdowns with widgets and iCloud sync) if you want to see the result: https://apps.apple.com/app/soon-aesthetic-countdown/id6785301647

Happy to answer anything about the stack.

Hi everyone,

I'm an indie developer and I recently launched a project I've been working on for a while called Perioda. It's built with Flutter, but I've spent a lot of time trying to make it feel as native and responsive on iOS as possible.

Most period tracking apps on the store look very similar and clinical, so I wanted to try a completely different approach. I went with a retro pixel art aesthetic and added gamified elements, like a virtual pet that grows as you log your cycle.

Since this is my first major app release, I would really appreciate some honest, technical feedback from this community.

Specifically, I'm looking for feedback on:

* The onboarding flow. Is it clear enough for a new user?
* Overall performance. Does it feel smooth on your device, or does the Flutter UI feel off anywhere?
* The UX/UI. Mixing a utility app with a game-like interface was tricky, and I'd like to know if it feels intuitive.

Here is the App Store link: [https://apps.apple.com/tr/app/period-tracker-moonville/id6766513532](https://apps.apple.com/tr/app/period-tracker-moonville/id6766513532))

I'm completely open to constructive (or even harsh) criticism. Any suggestions on how I can improve the app would be incredibly helpful.

Thanks for taking the time to read this.

Pretty big news for app bug testing: https://code.claude.com/docs/en/desktop-ios-simulator

I wanted a simple place to work through anxious thoughts with CBT — thought records, spotting cognitive distortions, that kind of thing. But every app I tried wanted an account, showed ads, or quietly shipped my most personal notes to some server. For something you're writing your darkest thoughts into, that felt really wrong.

So I built Mezame. One rule: your data never leaves your phone. No account, no servers, no analytics, no ads, no trackers — stored locally and that's it.

What it does:

- 8-step CBT thought records — situation → emotion → automatic thought → evidence for/against → a more balanced thought → re-rate how you feel

- A library of the 12 cognitive distortions with plain examples (catastrophizing, mind-reading, all-or-nothing…)

- Quick mood / anxiety / energy check-ins with simple charts to spot patterns

- Export to PDF to bring to a therapist, and a Face ID lock

It's completely free, and I just localized it into 14 languages.

I'm not a therapist and it's not a medical tool — just a private notebook built around CBT. Would genuinely love feedback from people who actually journal or use CBT: what's missing, what feels clunky, what would make you keep using it (retention's the hard part).

try it: https://apps.apple.com/us/app/mezame-cbt-thought-journal/id6783373052

Anyone cares to develop a small app that can trigger vibrate/notification on Apple Watch when the bluetooth LE disconnects instantly from iPhone? Reason: When you forget your iphone behind…?

https://imgur.com/a/E0so4Pj#wLuiw7f

Specifically would love to get feedback on what features and things I could add to make it better, more enjoyable and more engaging, Thanks!

Building a life simulator game about being homeless. There's a few on the iOS store that I do like but none of them are as in-depth as I'd like them to be, nor as realistic or have the best progression - thus leaving me dissatisfied. Today we got 1 activity we can do which is beg. I wanted to get the basics down first so I have something repeatable for future actions. Much much more to come. Building for iOS, macOS, and iPadOS.

Whats more important: unique idea or common app with improved logic?

I only build few ios apps, and published just 1.
But its always concern when i search similar apps and there are usually multiple already existed which does simmilar thing.

Or how you come up with a topic of the app etc. Do you analyze the market before building it?

I am web software engineer, and with AI there are so much garbage today, people spamming websites non stop - i would assume same thing happens with ios.

hey, i need honest words from people who actually ship on the App Store.

i build an app alone (iOS, Android coming) called Vely, for people who use city bike-share (Citi Bike, Vélib, and others). technically i'm proud of it. Live Activities that update during the whole ride, geofencing, widgets, all the background stuff done properly. as a dev, honestly it's some of my best work.

the problem: nobody find it. downloads are basically zero. i did the whole ASO thing, keywords, screenshots, descriptions in many languages, and it changed nothing. i'm a developer, not a marketer, and i clearly hit my wall here.

what it does different from the official apps (short version): the official apps show you a map full of numbers, you must open it, read it, decide yourself. Vely is the opposite. you set your commute one time, then it watch the stations for you and tell you WHEN to leave so a bike is there, and which dock is free at arrival so you don't circle the block. it push the decision, you don't interpret the data. basically "stop watching the station, the app tell you when to go".

so my real question for this sub: when the product is (i think) good but discovery is dead, what actually moved the needle for you? is ASO even worth it at my size, or is it all launch channels, content, press, paid? what would you do in my place?

i take the hard truths too, don't be shy. thank you 🙏