r/swift • • 5h ago

Project High school student building my first macOS app would anyone actually use this?

6 Upvotes

Hey everyone!

I'm a high school student currently working on my first ever app, called Due Ahead, built using Swift and SwiftUI.

The idea came from a problem I kept running into at school. Assessments and homework were scattered across student portals, emails, PDFs and random announcements, which made it pretty difficult to keep track of everything, especially when multiple assessments were due around the same time.

So I decided to try building something to solve it myself!

What I've built so far:

  • A weekly timeline showing upcoming assessments and deadlines.
  • Workload tracking based on estimated completion times.
  • Subject organisation to keep everything in one place.
  • Reminders for overdue and upcoming tasks.
  • A notes feature for quickly writing things down during class.
  • On-device AI summaries to help organise messy or rushed notes.
  • Local storage so everything works offline.

I'm developing the macOS version first, with the possibility of bringing it to iOS later.

A little about the development:

I've been using SwiftUI to build the interface and Apple's native frameworks wherever possible. One of my main goals is to make the app feel like it actually belongs on macOS rather than being a website wrapped in a desktop window.

It's still in beta, and I've got plenty to learn, but seeing something I built actually running as a native Mac app has been pretty exciting!

I'm mainly posting because I'd love to hear from other Swift developers.

A few things I'm curious about:

  1. Does the interface look and feel like a native macOS app?
  2. Are there any SwiftUI design or development practices you'd recommend for someone building their first app?
  3. Is there anything about the UI or feature set you'd approach differently?

I'm not looking to promote or sell anything here. I'm just interested in learning from more experienced developers and improving what I've built.

Any feedback, including criticism, would be really appreciated!

here are some photos of the app

Thanks for reading :)


r/swift • • 44m ago

Project I benchmarked my Swift memory library against the standard AI memory benchmarks, then spent weeks fixing it. Here are the before/after numbers.

2 Upvotes

I build Wax (https://github.com/christopherkarani/Wax). It’s a local memory store for AI agents and on-device models, written in Swift. Everything lives in one .wax file: documents, an FTS5 text index, Core ML vectors and a WAL. Claude Code, Codex and Cursor connect to it over MCP, and Apple Foundation Models get it as on-device tools. 0.1.51 shipped this week.

I spent the last few weeks running Wax against the standard memory benchmarks. The early numbers were bad, so most of the work went into fixing Wax. Every number below comes from the harness in the repo, and the scripts to reproduce it are there too.

Before and after (100k passages, M3 Max, importDocuments store):

BeforeAfter
Disk13.5 GB286 MB
Ingest136 docs/s57,250 docs/s
Vector search p9564–97 ms1.55 ms (p50 1.05 ms)
Cold open + first query840 ms108 ms
Recall@10 vs exact search0.9020.998

Retrieval quality:

  • LongMemEval-S: R_all@5 of 0.938, against 0.902 for Contriever (a 110M-parameter retriever).
  • LoCoMo: R_all@5 of 0.609, against 0.407 for Contriever. Before the fixes it was 0.186.
  • That’s with e5-small-v2 (33M parameters) and a 22 MB MiniLM cross-encoder reranker. Both ship as Core ML models computing in FP16 over INT8 weights, and both are on by default.

Against mem0 on LoCoMo QA: I ran open-source mem0 through the same reader, judge and scoring. Given the same amount of context (about 16.8k characters, which is Wax’s top 98 turns), Wax scored 77.7% and mem0 77.5%. To build its memories, mem0 made about 6,000 LLM calls at ingest. Wax made none: you store a sentence and hybrid search finds it later. The gap is within noise, so I’m calling it a tie, not a win.

The Swift API

The public surface is one actor, Memory. You open a file, save text, and search:

import Wax

let url = URL.documentsDirectory.appending(path: "agent.wax")
let memory = try await Memory(at: url)

try await memory.save("The user is building a habit tracker in SwiftUI.")
let results = try await memory.search("What is the user building?")
if let best = results.items.first {
    print("Found: \(best.text)")
}

try await memory.close()

On iOS 18 / macOS 15 and later, Memory(at:) loads the e5 embedder on its own; there’s nothing to configure. Search is hybrid by default: text and vectors fused, then reranked. Every result carries diagnostics, so you can see whether a query actually used vectors or fell back to text while the model was still loading. For bulk loads there’s importDocuments, which is where the 57k docs/s comes from. It’s atomic: if it throws or the app crashes, the store is left as it was.

Foundation Models

Apple’s on-device LanguageModelSession forgets everything between launches. Wax gives it a memory that survives restarts. One call gets you a session that recalls relevant memories into the prompt, has remember/recall/search tools, and can write turns back:

let memory = try await Memory(at: url)
let session = memory.foundationModelsSession(
    instructions: "You are a helpful assistant with durable on-device memory."
)
let answer = try await session.respond(to: "I prefer dark mode and Vim keybindings.")

If you already have your own session, just attach the tools:

let tools = memory.foundationModelsTools(kit: .focused)
let session = LanguageModelSession(tools: tools) {
    "You have long-term memory via waxRemember / waxRecall / waxSearch."
}

The model, the embedder, the reranker and the store all run on the device, with no network calls.

If you want to try it, add the package (https://github.com/christopherkarani/Wax.git, from 0.1.51), or run npx -y waxmcp@latest install to use the MCP server with Claude Code, Cursor or Codex. I’d love feedback, especially from anyone shipping on-device AI in Swift.


r/swift • • 18h ago

Some tips for the Swift Student Challenge 2027

2 Upvotes

I am taking part in this years challenge where the size limit is 500 mb. One thing that i wanted to ask is that should the judged be able to understand the core idea of our the project/ 4pp(reddit is stupid) in under 3 minutes or that they should be able to visit every inch of the 4pp within 3 minutes. My 4pps core idea could be understood in 3 minutes but visiting every inch of the 4pp, that might not be possible. Any suggestions would help a lot. any other tips for the challenge as a whole from experienced participants, winners or distinguished winner would be even more help ! thanks
Just a question how much AI is okay and how much is just not because in 2026 AI can make better things than someone who started learning siwft 3 months ago(me)


r/swift • • 21h ago

Question App testing in Testflight or App Store

1 Upvotes

Getting ready to release my first iOS app and will be looking for people willing to test it.

Generally do I ask them to test using TestFlight or do I need to have it on the APP store?

I will expect some bugs and feedback so I am prefer using TestFlight.

Comments or suggestions are appreciated.


r/swift • • 22h ago

SwiftExoPlayer

Thumbnail
github.com
1 Upvotes

I’ve been working on SEPlayer, a framework for building media players with almost all playback logic running entirely in userspace. Only decoding, video rendering, and audio playback are handled by the system.

I’ve spent two years researching and experimenting with different playback pipelines. Initially, I followed ExoPlayer’s approach, but its high-frequency timer-based pipeline isn’t particularly power-efficient.
I think I’ve finally found a better solution: an event-driven pipeline that only does work when necessary.
The project is still in alpha, and there’s a lot left to implement.

Currently supported:
Progressive MP4, fMP4, and MPEG-TS playback
HLS

Planned:
MPEG-DASH
Additional containers and formats, including Matroska, AVI, MP3, and raw AAC streams
More stability improvements, error handling, and tests

One of the main goals is extensibility. Unlike AVPlayer, SEPlayer allows you to implement your own demuxer, use different renderers, or replace the ABR algorithm, much like ExoPlayer.

There’s still a long way to go, but I wanted to share what I’ve been working on.
I’d be interested in hearing feedback, especially from anyone who’s worked on media playback pipelines or video players.


r/swift • • 21h ago

News I built Snitch, an open-source in-app inspector for network requests and analytics events (PostHog, AppsFlyer)

0 Upvotes

Hey r/swift,

For the past few weeks I've been working on a side project and wanted to share it here for feedback.

Snitch is a debugging tool you add to your iOS app. It shows every network request and every analytics event your app sends, right on the device. Shake the phone (or tap a floating button) and you get a timeline you can search and filter.

Why I built it: at work I kept asking "did that analytics event actually go out, and what was in it?" Answering that meant print statements, setting up a proxy, or staring at gzipped and encrypted payloads.

What it does:

- Captures URLSession traffic via URLProtocol, with headers, pretty-printed JSON bodies, search and filters
- Works with your own URLSessions and keeps their settings, so cookies, caching and SSL pinning still behave normally (auth challenges are forwarded to your session's delegate)
- PostHog events through its beforeSend hook, and each event links to the batch request that uploaded it (Snitch unzips the gzip body and matches event IDs)
- AppsFlyer events with zero code changes: it finds the SDK at runtime and wraps its public logEvent methods, so there's no AppsFlyer dependency
- Copy as cURL, pause recording, light and dark mode, Liquid Glass on iOS 26 with a fallback to iOS 16
- Debug-only: every call is a no-op without DEBUG, and nothing leaves the device

The core has zero third-party dependencies. Setup is one line: Snitch.start()

GitHub: https://github.com/BachoOnn/snitch

I also shared the story behind it on LinkedIn, with a few slides showing it in action:
Linkedin post

It's still early, so I'd really appreciate feedback, bug reports, or ideas for which SDK to support next (Firebase? Mixpanel?). Happy to answer questions about how any of it works.


r/swift • • 21h ago

Project Modification to Swift 6.4.1

0 Upvotes

Hello everyone.

i made Xwift, a cross-platform toolchain for the swift language based on swift 6.4.1.

you write the code once and the same source builds native apps for macos, linux and windows, plus webassembly for the web.

installers are out now for all three.

baiehclaca.github.io/xwift-web