u/QebApps

I have -Xfrontend -warn-long-function-bodies=275 set in Other Swift Flags, and one of my views recently tripped it hard: the body came in at around 506ms. Compile times were getting annoying.

I did not rewrite anything. I just pulled pieces out of body into separate computed properties: the main content, the transition, and the sheet modifier. Same code, same behaviour, just moved out of body.

The warning went away.

What surprised me is that there was no single monster expression to blame. body was just long, and the type checker seems to struggle with the accumulation rather than with one specific line. What helped was extracting one piece at a time and rebuilding, instead of refactoring the whole view at once.

So now I am wondering about the threshold itself. 275 is just the first number I tried. Too low and you drown in warnings on a big project, too high and you only find out when builds are already painful.

What do you use, and did you land on it deliberately?

I have two apps on the App Store, both small, both mine alone.

Every time an update is ready I get this knot in my stomach. In fact it starts in App Store Connect, filling in the version, the what's new, checking the screenshots for the third time. I don't know why that part gets me. Maybe because it's the only part where a mistake is public and stupid rather than technical.

The funny thing is I test, I have unit tests, I have beta testers who have been on the build for days and told me it's fine. I use the app myself every day. Rationally I know it's fine. I still sit there staring at the button.

Is it just me? Does this go away with time, or do you just get used to it?

Heard rumors about possible price hikes, so I pulled the trigger on a Sky Blue MacBook Air without ever seeing the color in person. Went to an Apple Store afterward just to check, and luckily I'm in love with the color.

Delivery estimate is early August, though. In fact I went with 32GB RAM and 1TB storage instead of the base config. Anyone know if there's a decent chance it ships earlier than that, or should I just settle in for the long wait?

Hey everyone,

I'm a solo developer, and over the past few months I've been building Newsairy, an RSS reader for iPhone, iPad and Mac — mostly to fix a personal pet peeve. I follow a lot of feeds, and every reader I tried was missing at least one thing I wanted, so I'd end up either drowning in an endless unread list or missing what actually mattered. I wanted a reader that adapts to me, instead of one more I have to adapt to.

A few things I focused heavily on:

Smart Feeds: group your articles by time — Today, Last 24 / 48 / 72 hours, Last 7 days, This week — so you can catch up by recency instead of scrolling forever.

Custom Smart Feeds: build your own keyword-based feeds that gather every matching article across all your sources.

Flexible reading: sort any list Newest first, Oldest first, or as a Daily timeline; pick a theme (including Sepia); customise the article list and the reading font/size; and find things again in Read History, sorted by when you read them.

Privacy-first: no ads, no tracking, no third-party analytics.

iCloud sync, no account: feeds, folders and read/unread state stay in sync across iPhone, iPad and Mac using your own iCloud — no sign-up, no separate account.

It's free to try with up to 6 local + 6 iCloud feeds. A single one-time purchase (no subscription) removes the limit and unlocks sync with TheOldReader, Miniflux, FreshRSS, Feedbin and Inoreader, bringing your existing subscriptions, read state and starred items with you.

This is a Discussion post as much as a share — I'd genuinely like to hear how you deal with RSS/news overload: do you lean on time-based catch-up, keyword filters, folders, something else? And what's the one feature your ideal reader would have that most apps get wrong?

Home page

App Store

Quick update on Newsairy, the iCloud-native RSS reader I've been building. Version 1.07 adds Inoreader sync — one of the most-requested aggregators since I started.

You all know the drill, so I'll spare you the spiel: full two-way sync across iPhone, iPad and Mac, OAuth login. I mostly added it as the native, no-nonsense companion for people who already live in Inoreader on the web.

I didn't post here about 1.06, so to catch up: it added a Font & Size panel for the in-app reader — pick the typeface (a curated set, or any font installed on your device) and either follow system Dynamic Type or set title size, body size and line spacing by hand. Search also got much faster and no longer freezes the list, even with thousands of articles.

A couple of things already in the pipeline, if you're curious: 1.08 ("Reading Flow") adds Last 7 days / This week Smart Feeds, per-feed and per-folder Mark All as Read, and article sorting — including a Daily timeline that reads each day oldest-to-newest. Then 1.09 brings Mark as Read on Scroll — which is on the roadmap because a couple of you asked for it right here on r/rss — plus cover images for feeds (Ars Technica and the like) that only expose them via media: tags rather than in the article body. Full roadmap's on the site.

For anyone who hasn't come across it: Newsairy syncs over iCloud across iPhone, iPad and Mac, and Pro adds sync with TheOldReader, Miniflux, FreshRSS, Feedbin and now Inoreader. One-time purchase, no subscription, no ads, no tracking.

I have a long todo list, but I'm always open to suggestions — if there's a feature or a use case you'd like to see, let me know.

App Store

>

I keep seeing "productivity apps" that are web-only, and I struggle to call them productivity tools. To me, productivity means capturing a task or idea the moment it happens — on the train, between meetings, away from a laptop. If the only way in is a browser tab, you've already lost that moment.

Native apps can also give you offline access and widgets.

Counterargument I get: "a good responsive web app is enough." Maybe, but how many web-only tools do you actually open daily vs. native apps?

Is mobile-native a dealbreaker for you, or am I overthinking this?

I just discovered this subreddit and wanted to share an article I wrote last August, when the debate was at its peak. Most of the arguments still hold — curious what people think now that iOS 26 is actually shipping.

Quick update on Newsairy, the iCloud-native RSS reader I've been building. Version 1.05 adds Custom Smart Feeds — a feature a few of you mentioned in the comments on an earlier post, so I moved it up the roadmap and shipped it sooner.

The idea (I'm sure you know, but just in case you want more details): create your own keyword-based feeds that pull together matching articles from across all your sources. You give each one a name, a colour, and one or more keywords — any article that mentions them in the title, summary, or content shows up there automatically. They behave like the built-in Smart Feeds (Today, Last 24/48/72h): unread count badge, and the usual read / unread / starred filters.

For anyone who hasn't come across it: Newsairy syncs over iCloud across iPhone, iPad and Mac, and Pro adds sync with TheOldReader, Miniflux, FreshRSS and Feedbin. One-time purchase, no subscription, no ads, no tracking.

I have a long todo list, but I'm always open to suggestions — and as this release shows, your comments do shape what I build next. If there's a feature or a use case you'd like to see, let me know.

App Store

Two weeks, two releases.

Newsairy is an RSS reader for iPhone, iPad, and Mac — built with SwiftUI:

• two weeks ago: launch with TheOldReader sync, few features but a solid foundation
• last week: 1.01 added Miniflux sync
• today: 1.02.0 adds FreshRSS sync and thumbnail size options in the Articles List (none, small, medium, wide)
• next: Feedbin sync and “Mark all as read”

My approach: keep releases small and focused, ship frequently, and let user feedback steer what comes next. The clearest example — “mark all as read” is going into the next release because three separate people asked for it in the first few days. I don’t use that feature myself, so I’d quietly deprioritised it. That’s exactly the kind of signal you can’t get before launch.

Anyone else using community feedback as a prioritisation tool?

Two weeks, two releases.

1.01 added Miniflux sync. 1.02.0, out today, adds FreshRSS sync and thumbnail size options in the Articles List (none, small, medium, wide).

My approach: keep releases small and focused, ship frequently, and let user feedback steer what comes next. The clearest example — "mark all as read" is going into the next release because three separate people asked for it in the first few days. I don't use that feature myself, so I'd quietly deprioritised it. That's exactly the kind of signal you can't get before launch.

I wrote about this in more detail here: https://qebapps.statichost.page/devnotes/ship-early-learn-fast/

Newsairy is an RSS reader for iPhone, iPad, and Mac — built with SwiftUI, syncs with self-hosted aggregators (Miniflux, FreshRSS, Feedbin coming next).

https://qebapps.statichost.page/newsairy/

Anyone else using community feedback as a prioritisation tool?

Newsairy 1.02.0 is out!

As promised, FreshRSS sync is here. If you're running your own FreshRSS instance, you can now connect it to Newsairy and keep your subscriptions, read state, and starred articles in sync — just like Miniflux.

Also new in this release: thumbnail size options in the Articles List Options — none, small, medium, or wide.

Coming up next:

• Feedbin sync
• More Articles List customisation
• Mark all as read — this was requested right here in the comments, thank you! It’s coming 🙏

Keep the feedback coming — it really does shape what gets built next.