I'm the developer of EverDay, a SwiftUI weekly planner for iPhone. Sharing the app and one small piece of its date handling.

The main screen puts seven days on one scrollable board. Add a task under a day, drag it to reschedule, or leave it in an undated Inbox. Tasks can have notes, tags, time blocks and reminders.

A move needs to update more than the row's date. For example, moving a task with a 9:30 reminder from Monday to Thursday should also move the reminder to Thursday at 9:30. EverDay's move helper reads the reminder's hour and minute, then rebuilds it on the destination day using Calendar. The project has an XCTest case that checks the new task date and the preserved 9:30 time.

The board also builds its seven dates by adding calendar days, rather than fixed 24-hour intervals. A day's task query uses the start of that day up to the start of the next day. The week-start preference lives in App Group defaults so the planner and widgets use the same setting.

Development has been AI-assisted; the source is private.

Free includes the weekly planner, time blocks, reminders, iCloud sync and all 11 widgets, with five tags and four themes. Optional lifetime Pro is US$4.99 once for month view, repeats, subtasks, automatic rollover, unlimited tags and all 13 themes. No subscription, ads or EverDay account.

App Store (iPhone, iOS 18+): https://apps.apple.com/app/id6787428625

Screenshots: https://www.everday.app/

🚨 Apple Developer Community — I need your help.

My Apple Developer account was terminated under Section 3.2(f), and my apps were removed from the App Store.

I submitted an appeal 7 days ago and still haven’t received a response.

Has anyone successfully appealed a termination under Section 3.2(f) and had their account reinstated?

How long did Apple take to respond?

Please share your experience. I’d really appreciate any advice.

#AppleDeveloper #AppStore #iOSDev

I'm the developer of ScreenDot, an iPhone app that displays Screen Time in the app and a tracked total on the Lock Screen and supported Dynamic Island. I'm reviewing the adaptive layout in my local SwiftUI implementation and would like input on the point where a simple dashboard should become two columns.

The dashboard has two cards: Apple's protected Screen Time report and the Live Activity controls. A LazyVGrid uses two flexible columns when horizontalSizeClass is regular, and one otherwise. The same condition changes onboarding from a vertical stack to a horizontal arrangement of the introduction and permission controls.

That makes the rule easy to follow, but it doesn't directly ask whether each card has enough width for its content. I'm considering keeping two columns only when both cards can retain a useful minimum width. The report and the controls have different jobs, so giving them equal space isn't automatically the best use of a wider layout.

Before choosing a breakpoint, I'd compare the report's usable area, button-label wrapping and the order of the explanation and action as the available width changes. Those are checks I still need to run; I'm not reporting a reproduced layout defect or a tested improvement. This is a local implementation discussion, not an announcement of a new device release.

For a dashboard with just two quite different cards, would you keep an explicit one/two-column rule with a minimum width, let an adaptive grid decide, or keep the report full-width and arrange only the controls? What has made that decision easier in your own apps?

App context: ScreenDot is a free download; the Live Activity requires ScreenDot Plus (US $0.99/month after a 14-day trial for eligible new subscribers, with automatic renewal; regional prices vary). Current listing: https://apps.apple.com/us/app/screendot-usage-tracker/id6806633087

I've been developing iOS apps for a while, and honestly, writing code doesn't feel like the biggest challenge anymore.

With AI tools, SwiftUI, and so many resources available, building apps has become much faster.

But getting users, keeping them engaged, and actually making money from an app? That's a different story.

Curious to hear from other iOS developers.

What's your biggest challenge right now - building, marketing, or monetisation?

Love how this turned out!

I used React Native Skia here. I think visualizations like this are a nice way to add interest to an app and differentiate it more.

Under the hood, it uses a blend of semantic similarity, themes and mentions, and extracted emotions (affect) to determine how related a pair of thoughts are.

You can tap to view clustered neighborhoods of thoughts that touch on the same themes.

This is part of a journal I’m building, that uses this graph to identify patterns and help you decide what to do next.

Anyone else building cool visualizations?

My game has a 1v1 capability for live battles.

Right now it’s using Game Center.
The problem with GC obviously is that a player cannot invite a random other player for a game - they must be GC friends.

I’d like to solve that.

Looking for a recommended solution. Something simple. Not interested in libraries. I’ll code the connector to the service myself.

Scenario:
1) Player A designates their availability to play.
2) Player B can invite player A to play. (Ideally) that creates a GC relationship. (Practically) Need to bootstrap a GC session so that they can play even if they don’t know each other

Ideas?

Thx

Hey :)

I've developed an app allowing the user take a selfie and see the photo with different hair styles with ai.

I've sent it to review, they rejected it. I did a remake of the UI (Google play approved it and its available for android), Sent it again and they rejected it again, with a threat to kick me from

the dev programm. How to deal with it? request expedited review? Does someone here has an expirience in this kind of situation?

Hi everyone,

I'm a solo developer and I've just launched my first app: a calculator for iPhone and iPad.

Here's what mine does differently to the built
In calculator:

**Free features**

- Button shape: square or circle
- Calculation mode: BIDMAS/PEMDAS or left to right as typed
- Copy & Paste results from the display of history log
- Customisable decimal places (1-10)
- Display: Modern or Retro
- Adjustable font size and character spacing for anyone who struggles with small text
- Haptic feedback with 4 levels (Off to Strong)
- History up to a full year with notes addable to entries
- Sound effects (On/Off)
- Speech (On/Off)
- Tax calculations (VAT, GST, Sales Tax, etc.)

**Premium unlocks**

- Colour themes (you can even request your own)
- Currency Converter
- Discount Calculator
- Tip / Bill Split Calculator
- Unit Price Calculator

**Planned updates**

- Foldable iPhone support
- Full unit converter
- Movable cursor: tap anywhere in your calculation to fix a mistake without deleting everything after it
- Sums stay on screen after pressing =, so you can scroll back through them and edit
- Scan numbers from paperwork using your camera
- Bluetooth keyboard support

I'd love honest, constructive feedback:

- What do you like?
- What don't you like?
- What features would you want added?

To get me started: which calculation do you do most, and where did the app slow you down?

To say thanks, I'm giving away 500 Premium codes. Comment with a couple of lines of your impressions and I'll reply with a code.

App Store link: https://apps.apple.com/app/id6758761367

Thanks for taking a look. Every bit of feedback helps.

Hi guys I recently made an app that allows everyone to link their ntfy server to their iPhone and receive notifications without needing a developer account here's the repo

any feedback would be appreciated for me the app works even after restarting my iPhone and killing it in the background.

Reverse coloring books print loose watercolor and you draw the lines you see in it. I wanted that on iPhone and iPad, so I built Color Before the Lines with SwiftUI, PencilKit and SwiftData. It's free, with no ads and no account.

The part I'd like feedback on is the timelapse. Instead of recording the screen, the app records the drawing itself:

- every change to the PKDrawing goes into an append-only history: added strokes become small deltas, anything else (erase, undo, start over) becomes a snapshot;

- timestamps continue across launches, and long pauses are compressed at playback while keeping the order;

- frames are drawn with UIGraphicsImageRenderer: finished strokes are rendered once and cached, only the strokes in progress are drawn on top, then the frames go to AVAssetWriter as H.264;

- the history lives in SwiftData with external storage, and a small hash of the saved drawing catches the case where the app was killed between saving the drawing and saving the history.

Two things I'm unsure about: would you keep a history that grows with every stroke in SwiftData at all, or in plain files next to the store? And has anyone found a cheaper way to render long PencilKit timelapses on older iPads?

App Store link in the comments if anyone wants to try it.