Just wanted to mark this moment.

As someone who had never written code before the AI era, reaching 200+ users and $100+ in sales in just 10 days feels unreal.

I’m grateful for AI and everyone on Reddit who inspired me along the way.

What an incredible era!

Here is what DiaryThread is:

Answer — what problem does it solve?

I kept abandoning journals because every blank page felt like it deserved a meaningful essay. Writing one short thought on my phone felt much more natural.

Diary Threads turns journaling into a private timeline. Each entry is limited to 140 characters. You can reply when a thought continues, quote something you wrote months ago, or attach photos, video, and voice recordings.

There are no likes, followers, public profiles, or social discovery. It is a timeline for one person.

Better — how is it different?

Compared with Apple Journal and Day One, Diary Threads focuses on a narrower use case: capturing a thought before it disappears.

The 140-character limit gives you a smaller starting point. Replies let one moment grow over time, while quotes make revisiting an old memory feel like a conversation with your past self.

Apple Journal and Day One remain stronger choices for long-form writing and broader ecosystem workflows. Diary Threads is designed for quick private posts that gradually become a personal history.

Diary text and settings stay on your iPhone. The app requires no account and has no developer backend, advertising, third-party analytics, or cross-app tracking.

Cost

Diary Threads is free to download and supports up to 30 active entries.

Premium unlocks unlimited entries, share posters, recurring keyword insights, and both Home Screen widgets:

• $2.99 per month

• $14.99 per year (save 58%), or $9.99 for the first year with code DIARYYEAR

• $19.99 one-time lifetime purchase

Prices above are for the US storefront. Apple displays the applicable regional price before purchase.

The current App Store version is 0.3 and requires iOS 18 or later.

Transparency

Diary Threads itself has no AI features. I used Codex extensively as a coding and review agent during implementation, testing, documentation, and iteration. Product scope, architecture, privacy boundaries, and acceptance decisions remained human-directed.

I’m Jack, and I built Diary Threads with Sonia.

App Store: https://apps.apple.com/us/app/diarythreads-personal-timeline/id6795139345

Website: https://diarythreads.niuniuhome.cn

About / developer identity: https://niuniuhome.cn

Contact: jackdai20@icloud.com

Hi, I’m Jack Dai, co-creator of Diary Threads.

Answer — what problem does it solve?

I kept abandoning journals because every blank page felt like it deserved a meaningful essay. Writing one short thought on my phone felt much more natural.

Diary Threads turns journaling into a private timeline. Each entry is limited to 140 characters. You can reply when a thought continues, quote something you wrote months ago, or attach photos, video, and voice recordings.

There are no likes, followers, public profiles, or social discovery. It is a timeline for one person.

Better — how is it different?

Compared with Apple Journal and Day One, Diary Threads focuses on a narrower use case: capturing a thought before it disappears.

The 140-character limit gives you a smaller starting point. Replies let one moment grow over time, while quotes make revisiting an old memory feel like a conversation with your past self.

Apple Journal and Day One remain stronger choices for long-form writing and broader ecosystem workflows. Diary Threads is designed for quick private posts that gradually become a personal history.

Diary text and settings stay on your iPhone. The app requires no account and has no developer backend, advertising, third-party analytics, or cross-app tracking.

Cost

Diary Threads is free to download and supports up to 30 active entries.

Premium unlocks unlimited entries, share posters, recurring keyword insights, and both Home Screen widgets:

• $2.99 per month

• $14.99 per year (save 58%), or $9.99 for the first year with code DIARYYEAR

• $19.99 one-time lifetime purchase

Prices above are for the US storefront. Apple displays the applicable regional price before purchase.

The current App Store version is 0.3 and requires iOS 18 or later.

Transparency

Diary Threads itself has no AI features. I used Codex extensively as a coding and review agent during implementation, testing, documentation, and iteration. Product scope, architecture, privacy boundaries, and acceptance decisions remained human-directed.

I’m Jack, and I built Diary Threads with Sonia.

App Store: https://apps.apple.com/us/app/diarythreads-personal-timeline/id6795139345

Website: https://diarythreads.niuniuhome.cn

About / developer identity: https://niuniuhome.cn

Contact: jackdai20@icloud.com

I’d especially appreciate feedback on one question: do replies and quotes make revisiting old memories feel more natural than tags, prompts, or traditional daily pages?

I’ve started and abandoned more journals than I can count.

The problem was rarely a lack of things to remember. Opening a blank page simply made every ordinary day feel like it needed a meaningful essay, while posting one short thought on my phone felt natural.

That led me to build Diary Threads, a private diary for iPhone that uses some of the interaction patterns of a social timeline.

Each entry is limited to 140 characters. You can reply when a thought continues, quote something you wrote months or years ago, or attach photos, video, or a voice recording. There are no likes, followers, public profiles, or social discovery. It is a timeline for one person.

Diary Threads also includes full-text and date search, calendar browsing, local writing analytics, App Lock, share posters, and two Home Screen widgets. Diary text and app data stay on the device, with no account, backend, advertising, or third-party analytics.

Tech stack

• Swift 6 and SwiftUI
• SwiftData for diary metadata
• PhotoKit for photo and video references
• AVFAudio for voice recordings
• LocalAuthentication for App Lock
• WidgetKit, App Intents, and an App Group for widgets and deep links
• StoreKit 2 for verified monthly and lifetime Premium access
• XcodeGen for project configuration

The first release has no backend. Photos and videos remain managed by the system Photos library, while the app stores their local identifiers. Voice recordings are stored as protected local files.

Development challenge: keeping a threaded SwiftUI timeline from becoming O(n²)

The timeline contains root entries, nested replies, quotes, direct reply and quote counts, descendant threads, and calendar day buckets.

A straightforward implementation would let each SwiftUI row scan the entire entry collection to calculate its reply count, quote count, quoted entry, and descendants. It looks harmless with ten entries. As the diary grows and SwiftUI reevaluates rows during scrolling, those repeated scans can turn presentation work into O(n²).

I solved this by building a DiaryPresentationIndex in one O(n) pass over the current entries. It prepares:

• Entry lookup by UUID
• Root entries
• Direct reply counts
• Direct quote counts
• Children grouped by parent UUID
• Entries grouped by calendar day

Home, thread detail, and calendar views reuse this index. Rows receive precomputed counts instead of searching the full collection. Descendant traversal follows the indexed child relationships with a visited set, then sorts the resulting thread once.

Search uses a similar separation. Search documents and localized date fields are prepared ahead of time, queries run as cancellable actor work, and generation counters ensure that only the newest query can publish results when someone types quickly.

This kept the SwiftUI views relatively simple and gave the relationship-heavy diary model one presentation source of truth.

Pricing

The free version supports up to 30 current entries, including root entries, replies, and quotes.

Premium unlocks unlimited entries, share posters, recurring keyword insights, and both Home Screen widgets:

• $2.99 per month
• $6.99 one-time lifetime purchase

AI disclosure

[AI-assisted]

I used Codex as a coding and review agent during implementation, testing, documentation, and iteration. I kept the product scope, architecture, privacy boundaries, and acceptance decisions human-directed.

The workflow relied on narrowly scoped changes, code review, unit and UI tests, localization checks, Xcode builds, and archive verification. AI made implementation faster; maintaining explicit product rules and verifying state-heavy behavior took most of the real work.

For developers working with relationship-heavy SwiftUI data: do you prefer persisting denormalized counts, calculating them during fetches, or building an in-memory presentation index when the source revision changes?

App Store: https://apps.apple.com/us/app/diarythreads-personal-timeline/id6795139345

I’ve started and abandoned more journals than I can count.

The problem was rarely a lack of things to remember. A blank page simply made every ordinary day feel like it needed a meaningful essay.

Posting one small thought on my phone felt much easier.

I started experimenting with a different format: one entry, up to 140 characters, placed on a private timeline. If the thought continued, I could reply to it. If something I wrote a year ago meant something different today, I could quote it and add a new note.

That experiment eventually became an iPhone app called Diary Threads.

It also supports photos, video, voice recordings, search, a calendar, and on-device writing patterns. There are no likes, followers, or public profiles. Diary text and app data remain on the device, with no account, server, ads, or analytics.

The free version supports up to 30 current entries. Premium will offer unlimited entries, share posters, keyword insights, and two Home Screen widgets through monthly and lifetime options.

Diary Threads is now available on the App Store:

https://apps.apple.com/us/app/diarythreads-personal-timeline/id6795139345

For people who journal on their iPhone: would replying to and quoting your past self make you revisit old entries more often? How do you currently keep a journal from becoming another archive you rarely open?

I’m launching an iPhone app called Diary Threads, and I’m trying to decide which part of the idea should lead the marketing.

The product came from a simple observation: writing a full journal entry often feels heavy, while posting one quick thought feels natural.

Diary Threads turns that behavior into a private diary:

- Entries are limited to 140 characters

- You can reply to an entry when a thought continues

- You can quote something you wrote months or years ago

- Photos, video, and voice recordings can live alongside text

- Search, calendar, and recurring keyword insights help resurface old memories

- Diary data stays on the device

- No account, server, ads, or analytics

The free version supports 30 current entries. Premium adds unlimited entries, share posters, keyword insights, and two Home Screen widgets, with monthly and lifetime options.

Right now I see three possible marketing hooks:

1. “Reply to and quote your past self”

2. “A 140-character private timeline”

3. “A diary with no account, server, ads, or analytics”

I’m leaning toward the first one because it explains the emotional value and the product interaction at the same time.

If you were positioning this for the App Store, which hook would you lead with? Does “private social feed” make the concept immediately clear, or does it create the wrong expectations?

I’ve started and abandoned more journals than I can count.

A blank page always felt like homework, while posting a quick thought felt natural. That made me wonder: what if a diary felt more like a private social feed?

So I built Diary Threads for iPhone.

Each entry can be up to 140 characters and lives on a personal timeline. When a thought continues, you can reply to it. When an old memory means something different a year later, you can quote it and add a new note.

You can also attach photos, video, or a voice recording. Over time, you can search everything you’ve written, revisit entries through a calendar, and see patterns such as writing frequency and recurring keywords.

There are no likes, followers, or public profiles. It’s a timeline for one person: you.

Diary text and app data stay on your device. Diary Threads has no account, server, ads, or analytics.

The free version supports up to 30 current entries. Premium adds unlimited entries, share posters, recurring keyword insights, and two Home Screen widgets, with monthly and lifetime options.

Diary Threads is now available on the App Store:

https://apps.apple.com/us/app/diarythreads-personal-timeline/id6795139345

Does replying to and quoting your past self make journaling feel easier, or does it make a diary feel too much like social media?

Hi everyone — I’m the developer of PasteItAll.

Clipboard history is useful when you need to recover something you copied a few minutes ago. I wanted a place for content I already know I’ll need again next week: reply templates, product descriptions, frequently used links, images, and reference files.

That became PasteItAll, a native macOS app built around deliberate saving.

PasteItAll does not build an automatic clipboard history or monitor everything you copy. When you press Control–Option–S, it reads the current clipboard once and opens a confirmation step.

It supports:

• Text and URLs
• Images and files
• Projects and tags
• Favorites, recent items, and search
• A Quick Picker opened with Control–Option–Space
• Menu bar and Spotlight access
• “Insert from PasteItAll…” through macOS Services in compatible host apps

The Services integration uses the standard request-specific pasteboard. The host app performs the insertion, so PasteItAll does not need Accessibility or Input Monitoring permission. Service visibility still depends on the host app, and the global Quick Picker remains available as the consistent fallback.

PasteItAll is written in Swift using SwiftUI and the AppKit integrations required for native macOS features. It is local-first, with no PasteItAll account, advertising, or remote analytics.

Pricing:

• The free version supports up to 7 saved items
• Pro unlocks unlimited saving
• Subscription and lifetime purchase options are available through the App Store

It requires macOS 15 or later.

I’d especially appreciate feedback on two parts of the experience:

1. Does deliberately choosing what to save feel useful alongside macOS Clipboard History?
2. Is the Services workflow discoverable enough, or would you rely mainly on the global shortcut?

Mac App Store: https://apps.apple.com/us/app/pasteitall-better-clipboard/id6792427586

Thanks for taking a look — honest criticism is very welcome. Leave me comments, and I will give some free Monthly-Subscription.

Hi everyone — I’m the developer of PasteItAll.

Clipboard history is useful when you need to recover something you copied a few minutes ago. I wanted a place for content I already know I’ll need again next week: reply templates, product descriptions, frequently used links, images, and reference files.

That became PasteItAll, a native macOS app built around deliberate saving.

PasteItAll does not build an automatic clipboard history or monitor everything you copy. When you press Control–Option–S, it reads the current clipboard once and opens a confirmation step.

It supports:

• Text and URLs
• Images and files
• Projects and tags
• Favorites, recent items, and search
• A Quick Picker opened with Control–Option–Space
• Menu bar and Spotlight access
• “Insert from PasteItAll…” through macOS Services in compatible host apps

The Services integration uses the standard request-specific pasteboard. The host app performs the insertion, so PasteItAll does not need Accessibility or Input Monitoring permission. Service visibility still depends on the host app, and the global Quick Picker remains available as the consistent fallback.

PasteItAll is written in Swift using SwiftUI and the AppKit integrations required for native macOS features. It is local-first, with no PasteItAll account, advertising, or remote analytics.

Pricing:

• The free version supports up to 7 saved items
• Pro unlocks unlimited saving
• Subscription and lifetime purchase options are available through the App Store

It requires macOS 15 or later.

I’d especially appreciate feedback on two parts of the experience:

1. Does deliberately choosing what to save feel useful alongside macOS Clipboard History?
2. Is the Services workflow discoverable enough, or would you rely mainly on the global shortcut?

Mac App Store: https://apps.apple.com/us/app/pasteitall-better-clipboard/id6792427586

Thanks for taking a look — honest criticism is very welcome. Leave me comments, and I will give some free Monthly-Subscription.

I kept searching the same places for content I had already used dozens of times: a product description in Notes, a reply template in an old chat, a useful link in a project document, or a file buried somewhere in Downloads.

Clipboard history helps answer, “What did I copy earlier?”

I wanted somewhere for, “What will I need again next week?”

So I built PasteItAll, a native macOS app for deliberately saving reusable content.

The main product decision is simple: PasteItAll does not monitor or record your clipboard in the background. It reads the clipboard only when you explicitly choose Save Current Clipboard.

The default shortcut is Control–Option–S.

You can save:

• Text and URLs
• Images and files
• Projects and tags
• Frequently reused replies, templates, links, and reference files

To find something again, press Control–Option–Space to open Quick Picker. Saved items are also available through the menu bar, Spotlight, and macOS Services in compatible apps.

PasteItAll is local-first. There is no PasteItAll account, advertising, or remote analytics.

The free version supports up to 7 saved items. Pro unlocks unlimited saving, with subscription and lifetime purchase options available through the App Store.

I’m the developer, and I’d especially appreciate feedback on the deliberate-save approach.

Would you use this alongside clipboard history, or does manually choosing what to keep add too much friction?

Mac App Store: https://apps.apple.com/us/app/pasteitall-better-clipboard/id6792427586

Hi, I’m Jack, the developer of PasteItAll, a native macOS app.

Full disclosure: this post is about my own app. I’m sharing it because the App Review fix changed how I think about cross-app features on macOS.

My first submission included a “direct paste” feature.

The original flow used Accessibility APIs to read the current selection, restore focus to the original app, and send synthetic copy or paste keyboard events through AX, PostEvent, and CGEvent.

It worked during development. Apple rejected build 7 under Guideline 2.4.5.

I decided to rebuild the interaction around APIs designed for Mac App Store distribution.

What I removed

• AX trust checks
• AXUIElement selection reads
• PostEvent permission requests
• Synthetic Command-C and Command-V events
• CGEvent insertion into another process
• The Accessibility permission flow and related settings

The global save shortcut became “Save Current Clipboard.” It reads the general pasteboard once, only after the user explicitly triggers the shortcut.

How insertion works now

PasteItAll now provides a standard macOS Service called “Insert from PasteItAll…”

The app declares NSReturnTypes for text, URLs, images, and file URLs. When the Service is invoked:

1. macOS provides a request-specific NSPasteboard.
2. PasteItAll opens its Quick Picker.
3. The user selects a saved item.
4. PasteItAll writes that item to the request pasteboard.
5. The host application’s responder chain receives the returned data and replaces the current selection.

The general clipboard stays untouched during native Service insertion. Command-Return remains available when the user only wants to copy the selected item.

One important product consequence

The host application controls whether the Service appears and whether it accepts the returned data.

That means the honest product promise is “native insertion in compatible apps that expose macOS Services.” It is not a universal paste mechanism.

TextEdit became my reference host. Other AppKit, SwiftUI, Electron, browser, and file-oriented hosts still need their own compatibility checks.

How I validated the change

• Scanned the Release archive for AX, PostEvent, and direct CGEvent symbols
• Reset TCC and confirmed the app produced no Accessibility request
• Verified the archived NSServices return types and timeout
• Added targeted tests for request pasteboards, cancellation, timeout, copy-only behavior, and write failures
• Kept host compatibility separate from unit and archive evidence

My main lesson was that passing sandbox and signing checks does not automatically make a cross-app interaction appropriate for App Review.

For features that modify content in another app, it helps to define which process owns the final mutation. With NSServices, PasteItAll provides the data and the host owns the insertion.

The redesigned version is now available on the Mac App Store:

https://apps.apple.com/us/app/pasteitall-better-clipboard/id6792427586

Apple documentation that guided the redesign:

https://developer.apple.com/library/archive/documentation/Cocoa/Conceptual/SysServices/Articles/overview.html

https://developer.apple.com/documentation/bundleresources/information-property-list/nsservices

For developers shipping Mac App Store utilities, which applications do you include in your NSServices compatibility matrix? I’m especially interested in the differences you have seen between AppKit, SwiftUI, Electron, and browser-based editors.

I kept looking for the same things across Notes, old messages, and random Finder folders: an email reply, an address, a useful link, a logo, or a file I send every week.

Eventually I wondered: what if I had one deliberate library for the things I actually reuse?

That became PasteItAll, a native macOS app I built with Codex.

PasteItAll saves only what you explicitly choose: text, links, images, or files. You can organize everything with projects and tags, then retrieve it through keyboard shortcuts, the menu bar, a Quick Picker, Spotlight, or macOS Services in supported apps.

The first working version came together surprisingly quickly.

Shipping it became a much bigger project.

The stack

• Swift 6
• SwiftUI
• AppKit
• SwiftData
• Core Spotlight
• App Intents
• Native macOS Services
• Xcode
• Codex

I started with a PRD and a small set of product rules. The most important one was simple: PasteItAll reads the clipboard only after an explicit user action.

From there, I asked Codex to work in vertical slices. Each system capability began with a protocol and a fake implementation, followed by the real macOS adapter and tests.

That workflow worked well for persistence, search, Spotlight indexing, localization, and most of the UI.

Then I reached cross-app insertion.

The feature that worked — until App Review

My first approach used Accessibility APIs and synthetic keyboard events to paste a selected item into another app.

It worked during local testing. The user triggered the action, the content appeared in the target app, and the interaction felt smooth.

Apple rejected version 0.1.0 under Guideline 2.4.5.

That rejection forced me to look at the feature from a platform perspective. The real question was deeper than “Does the code work?”

Who should own the insertion?

The answer was the host application.

I rebuilt the feature around standard macOS Services. PasteItAll now receives a request-scoped Pasteboard, opens its Quick Picker, writes the selected representation back to that Pasteboard, and lets the host application perform the insertion.

The revised implementation removed:

• Accessibility authorization
• Reading selections through AX APIs
• PostEvent access
• Synthetic copy and paste events
• Direct keyboard-event insertion

The interaction became more native, the permission model became smaller, and the architecture became easier to explain.

The revised build is currently going through final validation before App Store resubmission.

What Codex was good at

Codex was extremely useful for navigating a large Swift codebase, maintaining protocol boundaries, generating targeted tests, tracing requirements into implementation, and keeping documentation synchronized with code changes.

It also made iteration much faster. Once the system contract was clear, moving from an idea to a working vertical slice felt almost unfair.

Where I needed to take control

Platform semantics still required careful human judgment.

A generated implementation can compile, pass tests, and behave correctly on one Mac while still making the wrong architectural assumption about permissions, App Review, or another application’s responsibilities.

I also learned to treat these as separate pieces of evidence:

• The project builds
• Unit tests pass
• The signed archive contains the expected capabilities
• The feature works in a real host application
• The implementation satisfies App Review rules

One green checkmark cannot stand in for the other four.

What I would do differently

I would validate system boundaries before polishing the feature.

For a native app, I now want the earliest prototype to answer questions like:

• Which process owns this action?
• Which public API defines the interaction?
• What happens when the host app supports only some Pasteboard types?
• Does the signed Release archive match the source code I inspected?
• Can the feature work with fewer permissions?

Vibe coding made implementation dramatically faster. It also made it easier to travel a long distance in the wrong architectural direction.

The useful skill is learning when to stop prompting, inspect the system contract, and redraw the boundary.

Here’s PasteItAll if you want to see the result:

https://apps.apple.com/us/app/pasteitall-better-clipboard/id6792427586

For anyone shipping native apps with coding agents: has App Review or an operating-system rule ever forced you to redesign a feature that already worked?

I kept searching through old documents, messages, and folders for the same things: an email reply, an address, a useful link, a logo, or a file I send every week.

So I built PasteItAll.

It follows a simple rule: it saves only what you deliberately choose to keep. Your clipboard stays yours, and PasteItAll becomes a small, organized library for the things you know you’ll need again.

You can save text, links, images, and files, organize them with projects and tags, then retrieve them through:

• A fast Quick Picker
• The macOS menu bar
• Custom keyboard shortcuts
• Spotlight
• macOS Services in supported apps

PasteItAll is native, local-first, and built without accounts, ads, analytics, or background clipboard collection.

I’m giving 30 people one full year of PasteItAll Pro. I’m also looking for honest feedback while the app is still young.

If you discover a significant bug and send me a clear report with reproduction steps, I’ll give you Lifetime Pro as a thank-you.

The giveaway covers one year of Pro access. Please review any regional or renewal details shown by the App Store before redeeming.

App Store: https://apps.apple.com/us/app/pasteitall-better-clipboard/id6792427586

Reply in comment with “PasteItAll” — I’ll give one year of PasteItAll Pro to 30 commenters.

Never thought your handwriting could become the weather you see!

I’m the indie developer behind WeatherByYou, an iOS app that turns your handwriting into a personal weather widget.

Write each weather condition once—Clear, Cloudy, Rain, Snow, Thunderstorms, and more. WeatherByYou matches the current local weather to your handwriting and displays it on warm, paper-style Home Screen widgets.

What you can do:

• Create your own handwritten weather set
• Trace weather words directly on the writing canvas
• Choose different pen styles, colors, and thicknesses
• See live local weather in your own handwriting
• Add 2×2 and 4×4 Home Screen widgets
• Use the app in English, Simplified Chinese, or Traditional Chinese

Offer details:

• New users receive a 2-week free trial of WeatherByYou Pro
• After the trial, Pro automatically renews for $0.99/month unless canceled
• Pro unlocks unlimited handwritten weather sets
• The free version includes one complete handwritten weather set and both Home Screen widget sizes
• The subscription can be managed or canceled through your Apple Account settings

App Store:

https://apps.apple.com/us/app/weatherbyyou-draw-the-weather/id6785983208

I’d love to hear what you think, especially about the handwriting experience and how the widgets look on your Home Screen. Thanks for trying WeatherByYou!

Hey everyone,

I built Glance, a private iPhone app for rediscovering old photos in a more playful way.

Instead of scrolling through your photo library, Glance gives you daily memory packs. Each pack contains 5 random photos from before today. You tear open the pack, reveal the photos, then open any memory to see its time and place, write a note, or share a temporary copy through the iOS share sheet.

What Glance does:

• Daily memory packs with 5 old photos each
• Tear-to-open reveal interaction
• Photo date and location when available
• Private notes saved on your device
• History for revisiting revealed memories
• System share sheet for sharing a temporary copy
• No account, no ads, no tracking, no photo upload

Free mode includes:

• 3 memory packs per day
• Recent local History

Glance Pro includes:

• 10 memory packs per day
• Full local History

Promo:

• New eligible subscribers get 2 weeks free
• After the trial, Pro renews monthly at the App Store price shown for your region
• App Store: [https://apps.apple.com/us/app/glance-your-photo-memoir/id6783449883\]

I’d love honest feedback if you try it: the pack opening feel, the reveal flow, confusing parts, bugs, or anything you’d want in a photo memory app.

This started as a very small idea: I wanted a nicer way to remember walks with my dog.

Most pet apps I found felt either too medical, too social, or too heavy. I wanted something quieter: open the app, go outside, record the walk, keep the route and a few photos, then move on.

So I built PuppyTrail.

The app is basically a little journal for dog walks:

• walk routes, time, distance
• photos for starts, finishes, and little discoveries
• a monthly calendar of outings
• favorite places you want to go back to
• medals for distance, duration, and habits
• family sharing through iCloud

The most interesting part of the build was deciding what to remove.

At one point I had ideas for videos, complex social features, more health tracking, and a bunch of internal debug tools. The app got worse every time I tried to make it more “complete.”

The version I’m shipping is much more focused: make it easy to take the dog out, remember the walk, and share the memory with family.

Tech side:

• SwiftUI for the app
• MapKit + CoreLocation for routes
• CloudKit Sharing for shared dogs and history
• WidgetKit for quick home screen views
• AI tools for refactoring, localization, App Store copy, and checking edge cases

The hardest lesson: AI can generate screens quickly, but it won’t tell you which screen should exist. That part still has to come from watching the actual user behavior.

Would love feedback from people here on the product angle and the build story. I’m especially curious whether this feels like a real use case or just a cute niche app.

Link：https://apps.apple.com/us/app/puppytrail-record-your-puppy/id6766072770

This started as a very small idea: I wanted a nicer way to remember walks with my dog.

Most pet apps I found felt either too medical, too social, or too heavy. I wanted something quieter: open the app, go outside, record the walk, keep the route and a few photos, then move on.

So I built PuppyTrail.

The app is basically a little journal for dog walks:

• walk routes, time, distance
• photos for starts, finishes, and little discoveries
• a monthly calendar of outings
• favorite places you want to go back to
• medals for distance, duration, and habits
• family sharing through iCloud

The most interesting part of the build was deciding what to remove.

At one point I had ideas for videos, complex social features, more health tracking, and a bunch of internal debug tools. The app got worse every time I tried to make it more “complete.”

The version I’m shipping is much more focused: make it easy to take the dog out, remember the walk, and share the memory with family.

Tech side:

• SwiftUI for the app
• MapKit + CoreLocation for routes
• CloudKit Sharing for shared dogs and history
• WidgetKit for quick home screen views
• AI tools for refactoring, localization, App Store copy, and checking edge cases

The hardest lesson: AI can generate screens quickly, but it won’t tell you which screen should exist. That part still has to come from watching the actual user behavior.

Would love feedback from people here on the product angle and the build story. I’m especially curious whether this feels like a real use case or just a cute niche app.

Link：https://apps.apple.com/us/app/puppytrail-record-your-puppy/id6766072770

This started as a very small idea: I wanted a nicer way to remember walks with my dog.

Most pet apps I found felt either too medical, too social, or too heavy. I wanted something quieter: open the app, go outside, record the walk, keep the route and a few photos, then move on.

So I built PuppyTrail.

The app is basically a little journal for dog walks:

• walk routes, time, distance
• photos for starts, finishes, and little discoveries
• a monthly calendar of outings
• favorite places you want to go back to
• medals for distance, duration, and habits
• family sharing through iCloud

The most interesting part of the build was deciding what to remove.

At one point I had ideas for videos, complex social features, more health tracking, and a bunch of internal debug tools. The app got worse every time I tried to make it more “complete.”

The version I’m shipping is much more focused: make it easy to take the dog out, remember the walk, and share the memory with family.

Tech side:

• SwiftUI for the app
• MapKit + CoreLocation for routes
• CloudKit Sharing for shared dogs and history
• WidgetKit for quick home screen views
• AI tools for refactoring, localization, App Store copy, and checking edge cases

The hardest lesson: AI can generate screens quickly, but it won’t tell you which screen should exist. That part still has to come from watching the actual user behavior.

Would love feedback from people here on the product angle and the build story. I’m especially curious whether this feels like a real use case or just a cute niche app.

Link：https://apps.apple.com/us/app/puppytrail-record-your-puppy/id6766072770

This started as a very small idea: I wanted a nicer way to remember walks with my dog.

Most pet apps I found felt either too medical, too social, or too heavy. I wanted something quieter: open the app, go outside, record the walk, keep the route and a few photos, then move on.

So I built PuppyTrail.

The app is basically a little journal for dog walks:

• walk routes, time, distance
• photos for starts, finishes, and little discoveries
• a monthly calendar of outings
• favorite places you want to go back to
• medals for distance, duration, and habits
• family sharing through iCloud

The most interesting part of the build was deciding what to remove.

At one point I had ideas for videos, complex social features, more health tracking, and a bunch of internal debug tools. The app got worse every time I tried to make it more “complete.”

The version I’m shipping is much more focused: make it easy to take the dog out, remember the walk, and share the memory with family.

Tech side:

• SwiftUI for the app
• MapKit + CoreLocation for routes
• CloudKit Sharing for shared dogs and history
• WidgetKit for quick home screen views
• AI tools for refactoring, localization, App Store copy, and checking edge cases

The hardest lesson: AI can generate screens quickly, but it won’t tell you which screen should exist. That part still has to come from watching the actual user behavior.

Would love feedback from people here on the product angle and the build story. I’m especially curious whether this feels like a real use case or just a cute niche app.

Link in comments.