<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Thabo David Klass on Medium]]></title>
        <description><![CDATA[Stories by Thabo David Klass on Medium]]></description>
        <link>https://medium.com/@thabodavidnyakalloklass?source=rss-bf299d7ed1ac------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*2TT5vN6P5lD12LaiQW6M2Q.jpeg</url>
            <title>Stories by Thabo David Klass on Medium</title>
            <link>https://medium.com/@thabodavidnyakalloklass?source=rss-bf299d7ed1ac------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 12:58:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thabodavidnyakalloklass/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The only five things you need from any piece of paperwork]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/the-only-five-things-you-need-from-any-piece-of-paperwork-64eb10a82d7e?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/64eb10a82d7e</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[life-admin]]></category>
            <category><![CDATA[personal-finance]]></category>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[organization]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 16:22:21 GMT</pubDate>
            <atom:updated>2026-09-29T16:49:49.687Z</atom:updated>
            <content:encoded><![CDATA[<p>Everyone has a pile. Mine lives on the kitchen counter: an electricity bill, an insurance renewal, a school letter, an invitation to a toddler’s birthday party.</p><p>None of it is hard. The problem is that each document is a page of reference numbers, legal text and marketing, with the one or two lines that matter somewhere in the middle. Once you know what to look for and where it usually hides, the pile takes minutes instead of an afternoon.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0vaLvMFwEXy2f5A-enbCvw.png" /><figcaption>The DueTee app with an open task.</figcaption></figure><h4>The five things</h4><p>Every piece of life admin, whether it’s a bill, a letter, a policy or an invitation, comes down to five questions:</p><ol><li><strong>What is it?</strong> Who it’s from, and which account, vehicle, policy or person it’s about.</li><li><strong>What do I have to do?</strong> Pay, renew, attend, reply, or just keep it.</li><li><strong>By when?</strong> The date that actually matters, which isn’t always the one in large print.</li><li><strong>How much?</strong> If money is involved, the amount that’s actually due.</li><li><strong>What will I need?</strong> A reference number, a document, a booking.</li></ol><p>Everything else on the page is there for someone else’s benefit.</p><h4>Where the important parts hide</h4><p><strong>Bills</strong> usually carry several dates: the statement or issue date, the billing period, and the due date. Only the last one is a deadline. If you pay by debit order, the debit date is the one to watch; make sure the money is in the account the day before.</p><p>Amounts come in several versions too. <strong>Amount due</strong> is what you owe now. <strong>Balance</strong> may include charges that aren’t due yet. On credit cards, the <strong>minimum payment</strong> avoids a late fee, but interest keeps accruing on the rest.</p><p>On utility bills, check whether the reading is <strong>actual or estimated</strong>. Estimated readings can lead to a catch-up bill later, and that’s the one that hurts.</p><p><strong>Insurance renewals</strong> bury the useful part under the policy wording. Find four things: the renewal date, the new premium, the excess, and anything listed under changes to your cover. Compare them with last year before you accept.</p><p><strong>Appointment letters</strong> hide the practical details below the time and place. Is there anything to do beforehand, such as fasting, bringing documents, or getting a referral letter? Is there a cancellation window after which you’re charged?</p><p><strong>Invitations</strong> have two dates, and the one that matters to you first is usually the RSVP date, not the event. “Saturday 3 October” is the party; “RSVP by Thursday 24 September” is your deadline.</p><p><strong>Official letters</strong> tend to put the most important line last: the reference number to quote, the date you must respond by, and how you’re allowed to respond (online, in person, by post). If you miss the method, the date doesn’t help.</p><h4>A five-minute weekly system</h4><p>Once you know what to extract, the system is simple.</p><ol><li><strong>One inbox.</strong> Everything with a date goes in one place: a tray, a folder, one drawer. If paperwork can land in three places, you have to check three places.</li><li><strong>Extract on arrival.</strong> When something comes in, write the five answers on the envelope or put them in your calendar. That takes two minutes, and it’s the step everyone skips.</li><li><strong>Sort by date, not by type.</strong> Folders by category feel organized but hide urgency. A stack sorted by due date tells you what to do next.</li><li><strong>Look once a week.</strong> Pick a fixed time and look only at the next fourteen days. Pay it, book it, reply to it.</li><li><strong>Clear out what’s done.</strong> File it or bin it. A pile that only grows stops being useful within a month.</li></ol><h4>What to keep, and for how long</h4><p>This part varies by country, so treat it as a starting point rather than advice.</p><ul><li><strong>Paid bills:</strong> keep them until the next bill confirms the payment was received.</li><li><strong>Anything tax-related:</strong> keep it for as long as your tax authority requires, which is often several years.</li><li><strong>Insurance policies:</strong> keep them until they’re replaced.</li><li><strong>Receipts and warranties for major purchases:</strong> keep them until the warranty ends.</li><li><strong>Identity documents:</strong> keep them indefinitely, obviously.</li><li><strong>Invitations, appointment letters and reminders:</strong> bin them once the date has passed.</li></ul><h4>Where software fits</h4><p>Step 2, extracting on arrival, is the one that fails, so it’s the one I automated. I built an iPhone app called <strong>DueTee</strong>. You photograph a document and it answers the five questions for you: what it is, what action it needs, the deadline, the amount, and the text it read, so you can check what it found. It sorts the document into one of six categories and sets reminders a week before, the day before, and the morning it’s due.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P70eZ3aFjg0N8kt8XnVZVw.png" /><figcaption>The DueTee app’s settings.</figcaption></figure><p>It tells you when it isn’t sure, and holds anything unclear back for you to check. There’s no account, and your documents stay on your phone and in your own iCloud.</p><p>It’s coming soon to the App Store, with eight free documents a month. <strong>[</strong><a href="https://apps.apple.com/us/app/duetee-life-admin-tasks/id6809398738"><strong>Click here for DueTee AppStore</strong></a><strong>]</strong></p><p>The weekly look is still your job. No app replaces two minutes of attention once a week.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=64eb10a82d7e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Every renewal has two dates]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/every-renewal-has-two-dates-24cc17e2d615?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/24cc17e2d615</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[life-admin]]></category>
            <category><![CDATA[personal-finance]]></category>
            <category><![CDATA[iphone]]></category>
            <category><![CDATA[insurance]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Thu, 24 Sep 2026 16:20:47 GMT</pubDate>
            <atom:updated>2026-09-29T16:50:32.761Z</atom:updated>
            <content:encoded><![CDATA[<p>My car licence renewal notice arrived last month, the way it does every year. I read it, thought “that’s weeks away,” and put it somewhere safe. Somewhere safe is where paperwork goes to die.</p><p>This year I didn’t miss it, and the reason turned out to be more interesting than the app I used. It comes down to noticing that every renewal has two dates, and the letter only gives you one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r35E7db2U-oiwNGAuMbgJQ.png" /><figcaption>Crucial notifications from the DueTee app.</figcaption></figure><h4>The date on the letter is the wrong date</h4><p>Every renewal notice gives you a deadline. What it doesn’t tell you is when you need to start. Call that the <strong>act-by date</strong>: the deadline minus however long the renewal actually takes.</p><p>For some renewals that gap is ten minutes. Paying a vehicle licence online is quick, if your authority allows it. For others it’s weeks:</p><ul><li>A passport.</li><li>Anything that needs an in-person appointment.</li><li>Anything that needs another document first: a roadworthy certificate, a proof of address, a new photo, a form signed by someone else.</li></ul><p>A reminder set for the deadline is useless for those. By the time it goes off, you’re already late.</p><p>So the first rule: <strong>for every renewal, write down two dates.</strong> The deadline, and the act-by date. Set your reminder for the second one.</p><h4>The renewals people miss</h4><p>The ones that catch people out tend to fall into a few groups.</p><ul><li><strong>Vehicle licences and registrations.</strong> They’re annual, so no habit forms, and missing one can mean a fine or a car you can’t legally drive.</li><li><strong>Driving licences.</strong> These have the opposite problem. The validity is so long that when renewal comes round, you’ve forgotten how the process works and what it requires.</li><li><strong>Passports.</strong> Many countries won’t let you enter unless your passport is valid for months beyond your trip, commonly six. That means the deadline that matters for travel can be well before the expiry date printed in the passport. Check your destination’s rules before you book, not after.</li><li><strong>Insurance</strong> on your car, home or contents. A lapse creates a gap in cover you won’t notice until you need to claim.</li><li><strong>Professional registrations and memberships,</strong> where a lapse can quietly stop you working.</li><li><strong>Domain names.</strong> If a payment card on file has expired, the renewal fails silently.</li><li><strong>Free trials</strong> that turn into paid subscriptions, and warranties with a claim deadline. Neither is a renewal, but they work the same way: a date that matters, buried in something you read once.</li></ul><h4>Renewal day is also a pricing day</h4><p>Many renewals are also the moment a price changes, and that’s the part people don’t read.</p><p>Insurance renewal letters in particular deserve more than a glance. Compare the new premium with last year’s. Check whether the excess, the cover or the listed drivers have changed; insurers usually put this in a section with a title like “changes to your policy.” Then get at least one other quote. The same applies to subscriptions that renew at a higher rate after an introductory period.</p><p>You can only shop around if you notice the renewal before it goes through. That’s the second reason the act-by date matters: it leaves time to compare prices, not just to complete the paperwork.</p><h4>A six-line renewal checklist</h4><p>When a renewal notice arrives, while it’s still in your hand:</p><ol><li><strong>What</strong> is being renewed, and for which vehicle, policy or account?</li><li><strong>Deadline.</strong></li><li><strong>Cost</strong>, and whether it changed from last time.</li><li><strong>What you need</strong> to complete it: documents, an appointment, other certificates.</li><li><strong>Lead time</strong>: how long step 4 realistically takes, including queues.</li><li><strong>Act-by date</strong> = deadline minus lead time. Your reminder goes here.</li></ol><p>That’s about sixty seconds of effort, and it’s the part everyone skips.</p><h4>How I handle it now</h4><p>I write software for a living, so I built the tool I wanted. It’s called <strong>DueTee</strong>. You photograph the notice, and it gives you back a card: what it is, what it costs, when it’s due, and what action it needs (pay, renew, attend). Reminders follow automatically: a week before, the day before, and the morning it’s due.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MvhK053WNvm-R08D9QiOeg.png" /><figcaption>The DueTee app’s dashboard.</figcaption></figure><p>For a quick renewal like my licence disc, that’s enough. DueTee read the notice and showed me a confidence score and the exact text it had read, so I could check the date against the paper in five seconds. A week out, my phone reminded me, and I renewed.</p><p>For renewals with a long lead time, the app doesn’t know that your passport office takes six weeks; you do. Edit the deadline to your act-by date, or add a note. It takes a couple of taps.</p><p>Two design decisions matter here. First, <strong>it tells you when it isn’t sure.</strong> Anything it can’t read confidently goes to an Action Required list for you to check before any reminder is set. Second, <strong>it doesn’t need to know who you are.</strong> There’s no account and no sign-up. Text is read on your phone first, and card and ID numbers are removed before the text is sent for processing. Your documents stay on your phone and in your own iCloud.</p><p>DueTee is coming soon to the App Store, with eight free documents a month. <strong>[</strong><a href="https://apps.apple.com/us/app/duetee-life-admin-tasks/id6809398738"><strong>Click here for DueTee AppStore</strong></a><strong>]</strong></p><p>And if you’d rather not use an app, use the checklist above. The two-date rule is what does the work; the app just makes it faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=24cc17e2d615" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Triumph of the Nerds Never Really Ended]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/the-triumph-of-the-nerds-never-really-ended-4622aebc4002?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/4622aebc4002</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[history]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[nostalgia]]></category>
            <category><![CDATA[indiedev]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Fri, 07 Aug 2026 18:03:56 GMT</pubDate>
            <atom:updated>2026-08-07T18:05:08.822Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://www.primevideo.com/detail/0MOFU8XTB2FN5SHAFCFNL6JPOL"><em>The Triumph of the Nerds</em></a> was on TV one afternoon when I was fourteen or fifteen, and I’ve been thinking about it — once in a while — ever since. I re-watched it in the early 2010s — <a href="https://www.cringely.com/">Bob Cringely</a> walking around Palo Alto, Silicon Valley, Redmond, talking to Woz and Gates and everyone else in between. What that documentary did — and what I think most viewers missed at the time — was frame the personal computer revolution as an act of individual authorship. There was no product management. There was no market research. There were people, and there were machines, and there were things the people wanted the machines to do that the machines couldn’t yet do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rXKqUooT9eoWew-UZNAeHg.avif" /><figcaption>Winamp running on windows ’98 (<a href="https://www.xda-developers.com/winamp-open-source/">https://www.xda-developers.com/winamp-open-source/</a>)</figcaption></figure><p>I write this from Maseru, where I’ve been spending most of my nights for the past two months building a little Mac utility called <a href="https://apps.apple.com/us/app/senqu-image-converter/id6772722134?mt=12">Senqu Image Converter</a>. It converts and compresses images. That’s the whole product. It doesn’t sync to a service, doesn’t require an account, doesn’t phone home. When I first shipped it, a friend said it reminded him of <a href="https://en.wikipedia.org/wiki/Winamp">Winamp</a>. He wasn’t talking about the interface — Senqu doesn’t look anything like Winamp. He meant the feel. The sense that this was made by a specific person who used it themselves.</p><p>That comparison has stuck with me. I want to unpack it, because I think the story of how we got here — from Winamp and <a href="https://en.wikipedia.org/wiki/PaintShop_Pro">Paint Shop Pro</a> to <a href="https://tinypng.com/">TinyPNG</a> and back to something like Senqu — is more interesting than the usual “software used to be better” nostalgia. It’s a story about what the industry decided software was for, and about the pockets where that decision is quietly being questioned.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*ONL-1kd3dNXvgxXNvq0wyQ.png" /><figcaption>Paint Shop Pro 4 (<a href="https://winworldpc.com/product/paint-shop-pro/4x">https://winworldpc.com/product/paint-shop-pro/4x</a>)</figcaption></figure><h3>The ethos of the personal computer era</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/1*MJnFn02TfGRwngAN7Z9l4Q.avif" /><figcaption>Gary Kildall on The Computer Chronicles. (<a href="https://www.styletech.net/post/gary-kildall-the-story-of-the-forgotten-genius-who-invented-the-pc-operating-system">https://www.styletech.net/post/gary-kildall-the-story-of-the-forgotten-genius-who-invented-the-pc-operating-system</a>)</figcaption></figure><p>Cringely’s documentary is remembered for its Jobs-and-Gates dramatics, but it’s actually a series of quieter portraits of a specific ethos. The people building personal computers in the late 70s and early 80s were not building products in the modern sense. They were making things because the things did not exist yet, and because they, personally, wanted them to.</p><p>Woz building the Apple I in his garage. Gates and Allen writing BASIC for the Altair on a PDP-10 they didn’t own, based on a manual they’d read in a magazine. Adam Osborne building the first mass-market portable computer out of parts and audacity. Dan Bricklin writing VisiCalc because he was watching his professor at Harvard update a chalkboard spreadsheet and thought, this could be a program. None of these people were solving markets. They were solving personal problems that turned out to be everyone’s problems.</p><p>Gary Kildall belongs in this story and is almost always left out of it. Kildall wrote CP/M, the operating system that most microcomputers ran before MS-DOS. He was, by every account, a brilliant engineer with a genuine interest in getting the technology right rather than in the business game around it. When IBM came calling in 1980 looking for an operating system for their new personal computer, they went to Kildall first. What happened next has been argued about for decades — he was flying his plane, his wife handled the meeting, he was uninterested, IBM was insulted, take your pick of the narrative — but the outcome was that IBM went to Microsoft instead, Gates bought QDOS from another company for fifty thousand dollars, licensed it to IBM, and the rest is the industry we live in. Kildall died in 1994 in a bar in Monterey. Most software histories now give him a paragraph — a tragedy.</p><p>I mention Kildall not to re-litigate any of that, but because he represents something the industry moved past very quickly. He was a technologist who cared about the technology. He wasn’t cut out for the negotiation-and-lock-in game that Gates was extraordinary at. The industry rewarded Gates, not Kildall. Both were part of the ethos of the early personal computer era, but only one style of participant went on to define the next forty years. I’m not Gates-bashing — he’s done amazing things, undeniably. I’m just naming something that most of us who grew up loving computers don’t like.</p><p>The people I’ve mentioned — Woz, Gates, Osborne, Bricklin, Kildall, and the many others Cringely interviewed — did not agree with each other about much. They had different politics, different business instincts, different senses of what mattered. But they shared a working belief that a person could build a thing that would matter, without needing permission from anyone, and that the thing itself was the point. Someone would show up with an idea, they’d build it in a garage or a spare bedroom, and the world would be slightly different afterward. That belief is what “personal” in “personal computer” originally meant. It wasn’t about the size of the machine. It was about who was making it, and why.</p><h3>Paint Shop Pro and the shareware world</h3><p>The generation of software that came out of this ethos, in the 90s, made the shareware era possible. You probably don’t remember Paint Shop Pro if you’re younger than about 35. In the 90s, if you had a PC and you needed to edit an image, and you couldn’t justify Photoshop’s price, you used Paint Shop Pro. It was made by a small company called <a href="https://en.wikipedia.org/wiki/Jasc_Software">Jasc Software</a> in Minnesota. It cost sixty-nine US dollars for a registration. You could try it for free first. When you registered, they mailed you a serial number. I know — it’s quaint — but this is how software worked.</p><p>Paint Shop Pro was, by any modern standard, deeply weird. The UI was crowded. It had approximately one hundred and forty ways to do the same thing. It came with a batch converter, a screen capture tool, and an animation editor that most people never used. But it was made by people who used it themselves, and every quirk in it existed because someone at Jasc had wanted that quirk. If you sent them an email, you would get a reply. (Hell, if you sent an email back then, a sitting president would reply.) If you found a bug, someone at Jasc would fix it. It felt like a thing, made by other things, for you.</p><p>There were dozens of applications like this in the 90s. WinZip. Winamp. mIRC. Eudora. Homesite. UltraEdit. Kai’s Power Tools. On the Mac side, BBEdit, GraphicConverter, Interarchy, and dozens more. They were all made by tiny teams. They all cost between fifteen and eighty dollars. They all had personality. You developed relationships with them. Some are still around. Most are not.</p><p>The people who made this software were the direct descendants of the personal computer generation. They didn’t have Cringely’s cameras following them around, but they were doing the same thing: identifying something they personally wanted, and building it. The distribution channel was different — CyberCash for payments, Info-Mac Digest for word of mouth, PC Format and PC World magazine cover CDs for discovery — but the model was recognizable. A person had an idea, wrote the code, released it, and the world was slightly different afterward.</p><h3>What a single developer could do</h3><p>Somewhere between the shareware world and the Photoshop-vs-GIMP endgame, there was a brief moment when it became clear that a single developer could do something that would shake an entire industry. <a href="https://en.wikipedia.org/wiki/Justin_Frankel">Justin Frankel</a> wrote Winamp in 1997 at age eighteen — one guy, one MP3 player, and within a few years millions of people had it installed. AOL bought Nullsoft, the company Frankel had spun up around it, for eighty-six million dollars. Frankel then worked from inside AOL and released a peer-to-peer file-sharing tool called Gnutella. AOL made him take it down within hours. The internal message was clear: you work here now, and this is not what we do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*onFq81JWNpoKNAFHljViKA.jpeg" /><figcaption>Justin Frankel, creator of Winamp. (<a href="https://user.cockos.com/~deadbeef/?viewstart=492">https://user.cockos.com/~deadbeef/?viewstart=492</a>)</figcaption></figure><p>Shawn Fanning wrote <a href="https://en.wikipedia.org/wiki/Napster">Napster</a> in 1999 while still in college. Napster had, at its peak, about eighty million registered users. It didn’t so much disrupt the music industry as detonate under it. The lawsuits, the Metallica press conference, the eventual shutdown — all of that is well documented. What’s less remembered is that Napster was, mechanically, a very simple piece of software. It was a search index and a file transfer protocol. What made it consequential was that Fanning built the thing and released it, without asking the recording industry’s permission, and once it existed, it couldn’t really be undone. He was nineteen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/825/1*idchCA0qPlQTzGI71xzy2w.jpeg" /><figcaption>Shawn Fanning at the VMAs.</figcaption></figure><p>There was a specific cultural moment around this, and <em>The X-Files</em> caught it. In the 1998 episode “Kill Switch,” written by William Gibson and Tom Maddox, a reclusive programmer named Donald Gelman has created an AI so consequential that shadowy government interests are trying to kill him for it. Gibson and Maddox understood, better than most people at the time, that individual programmers were becoming figures of real cultural fascination and anxiety. Not because they were villains, but because they represented an intolerable proposition: that a person, alone, could build a thing that could not be recalled, controlled, or bought off. The old industries — record labels, phone companies, TV networks — were built on gatekeeping. The programmer was the person who could quietly render the gate unnecessary.</p><p>Frankel and Fanning were the shareware ethos scaled up. They were not making sixty-nine-dollar utilities; they were making things that reordered whole industries. But they were operating from the same working belief: identify something you personally want, build it, release it, see what happens. The difference was that at their scale, “see what happens” meant lawsuits, acquisitions, and eventually the industry closing ranks against the model that had produced them.</p><h3>The two possible endings for professional software</h3><p>While the shareware world was doing what it was doing, Photoshop was becoming Photoshop. Adobe understood something the small players didn’t fully grasp: professional workflows are stickier than individual purchases. A designer who learns Photoshop uses Photoshop for the next twenty years. A studio that standardises on Photoshop keeps buying licenses. By the mid-2000s, Photoshop had become the professional standard for image editing and the ambient reference point for everyone else. Even people who used Paint Shop Pro would say things like “it’s basically Photoshop but cheaper.” Photoshop had become the meaning of image editing.</p><p><a href="https://www.gimp.org/">GIMP</a> started in 1995 as a very different response to the same landscape. Two students at Berkeley, Spencer Kimball and Peter Mattis, built it partly as a class project and partly out of the belief that image editing shouldn’t be locked behind Adobe’s pricing. GIMP became the flagship of a specific ideology: software as a common good, license fees as coercion, source code as inheritance. Its user interface was famously idiosyncratic. It didn’t want to be Photoshop. It wanted to be free.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/670/1*9ShRhdlYuUDv27xRxSUuow.avif" /><figcaption>GIMP 9 running on Mac. (<a href="https://www.makeuseof.com/tag/gimp-photo-editing/">https://www.makeuseof.com/tag/gimp-photo-editing/</a>)</figcaption></figure><p>These two apps — Photoshop and GIMP — represent something worth naming. They were the two possible endings for professional software. Either you consolidate the market and turn the tool into an institution, or you refuse to play the market game at all and turn the tool into a manifesto. Both are legitimate. Both have survived. Neither has room for a Paint Shop Pro anymore.</p><p>The shareware ethos didn’t lose to Photoshop or GIMP directly. It got squeezed on both sides. Professional users went to Photoshop because their schools and studios required it. Ideologically-motivated users went to GIMP because it was free. Everyone in the middle — the Paint Shop Pro user who wanted a good tool from a small company they liked — quietly disappeared as an economic category. Not because the tools got worse. Because the middle stopped being a viable place to run a business.</p><h3>What TinyPNG represented, and what it took</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dxdx18hSd33FhsARFUVbNw.png" /><figcaption>TinyPNG at <a href="https://tinypng.com/">https://tinypng.com/</a></figcaption></figure><p>Around the early 2010s, something else started happening. A quieter shift, easy to miss. The image-editing task didn’t need to be a whole application anymore. If you just wanted to compress a PNG, you could go to a website called TinyPNG. You’d drag your file in. A second later, you’d get a smaller file back. Free. No install. No registration. No serial number in the mail.</p><p>This was genuinely good. I saw it and thought it was amazing. Why didn’t I think of it? TinyPNG is well-run. The compression is excellent. Millions of people benefited from it and still do. If you compress a PNG in 2026, the odds are decent that you’re using TinyPNG or one of its equivalents. It was a real innovation.</p><p>But something happened at the same time, and it took a while for anyone to notice. The image was no longer being processed on your machine. It was being uploaded to a company’s servers, processed there, and downloaded back. For a screenshot of a meme, this is fine. For a photo of your child, or a scan of a lease, or an ID document you needed to email to a client, it’s a different kind of transaction. You were now uploading files you cared about to a company you’d never heard of, running on infrastructure you couldn’t audit, subject to a privacy policy you didn’t read.</p><p>Most people didn’t notice because most files aren’t sensitive. But the shift was real. Image editing had gone from a thing you did on your machine to a service you consumed. The individual craft model of Paint Shop Pro was gone. Photoshop was still Photoshop. GIMP was still GIMP. But the whole middle — the personal utility that just sat on your computer and did its job — was hollowed out. You didn’t need it. There was a service.</p><p>The same thing happened to a lot of software categories in the 2010s. Notepad became Google Docs. Winamp became Spotify. Eudora became Gmail. Photoshop got a subscription and Lightroom got a cloud. What was once a personal thing you owned became a service you rented, running on someone else’s computer, requiring an internet connection to use.</p><h3>What got lost in the transition</h3><p>I want to be careful here, because “software used to be better” is a lazy argument that ignores real gains. Cloud services made a lot of work easier and cheaper for a lot of people — including me. The internet did not steal your soul. Google Docs is a genuinely useful invention, and it makes collaboration possible in ways that were previously very hard.</p><p>But something did get lost, and I think we’re only starting to see it clearly. When your image editor is a website, you can’t use it without an internet connection. You can’t use it offline in a rural clinic. You can’t use it on a plane. You can’t use it if the company goes out of business, which happens all the time. You can’t use it if the company decides to change its pricing, add ads, add a login wall, sell to a private equity firm, or shut down the free tier. You can’t use it if the file is one you don’t want to upload.</p><p>The Paint Shop Pro model, for all its quirks, had one property that the TinyPNG model doesn’t: the software belonged to you. You bought it. You installed it. You could use it for ten years without anyone’s permission. If Jasc went out of business — which it eventually did, absorbed by Corel — your copy still worked. That’s not a small thing. That’s a specific way of relating to your tools that we quietly gave up somewhere between 2005 and 2015, and I don’t remember voting on it.</p><p>The ethos I described earlier — the one Cringely captured, the one Kildall and Woz and Bricklin and dozens of others exemplified — had at its core the idea that a person could make a thing, and once made, the thing belonged to whoever wanted it. That model was quietly replaced with something else. Something where the thing you use lives on someone else’s server, is controlled by someone else’s policies, and can be taken from you at any time. This is not necessarily worse for every use case. But it is different, and worth noticing.</p><h3>Where Senqu fits in</h3><p>I’m not going to pretend <a href="https://apps.apple.com/us/app/senqu-image-converter/id6772722134?mt=12">Senqu</a> is a revolution. It’s a small utility that converts images, on your Mac, without uploading anything. It costs $4.99. It’s made by one person — me — in a small country in southern Africa. If Paint Shop Pro had a baby in 2026, it would look something like Senqu.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FjOQqhMG-umw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DjOQqhMG-umw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FjOQqhMG-umw%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1ae9885cba92c76e0cd99c94b889a3eb/href">https://medium.com/media/1ae9885cba92c76e0cd99c94b889a3eb/href</a></iframe><p>I didn’t set out to make an ideological statement when I started building it. I set out to solve a personal problem: I kept converting screenshots and I didn’t want to keep going to a website. I built the smallest thing that would do the job. When I was done, some users found it, told me what was wrong with it, and I fixed those things. A writer at Six Colors agreed to mention it. Other users showed up. Someone in the Podfeet community bought it and sent me feedback within hours. The whole cycle felt like something from a different era, because it was. This is how software used to be made, before we all agreed that the goal was to grow to a billion users and get acquired.</p><p>I don’t think this model is coming back at scale. Photoshop is not going anywhere. TinyPNG is not going anywhere. Most people will continue to use cloud services for most things, and that is probably fine. But there is a specific kind of user who has quietly started to want their tools to belong to them again. A specific kind of file — the lease, the scan, the photo of the child, the blood test — that they don’t want to upload. A specific kind of relationship with software that they miss without necessarily being able to name. That feeling that there were things that you owned, things that you could hold in your hand, parts of yourself that were yours only.</p><p>This isn’t only about software. We used to own CDs. We used to own DVDs. We used to own the music that played from our shelves and the movies that lived in a stack next to the TV. Now most of us rent access to those things from streaming services that can pull the licenses at any moment, remove titles without notice, raise prices whenever they like, and eventually shut down and take everything with them. I was mid-way through last year’s <em>Survivor Australia: Redemption</em> when it just vanished from one of our local streaming services. Now I use a VPN to finish it off — I’m a proud denizen of Perth every day, for about an hour. Streaming is convenient — genuinely — but it’s not ownership. My parents’ generation had a shelf of records they could still play if the power came back on. My late father’s records are still stacked in my Mom’s garage — should my three year old want them in the future; there they are. My generation, at some point, agreed to a different arrangement, and now we own almost nothing. The trade was real. So was the loss.</p><p>For those users, small local utilities are becoming relevant again. Not as a movement, not as a manifesto, but as an option that’s worth existing. Signal is not going to replace WhatsApp. ProtonMail is not going to replace Gmail. Senqu is not going to replace TinyPNG. They don’t need to. They just need to be there, running quietly on the machines of the people who want them.</p><h3>Closing</h3><p>I write indie code at night in Maseru. Some of what I write is for clients who pay me, and some of what I write is Senqu, which will never make me rich and doesn’t need to. It reminds me of watching Cringely’s documentary as a teenager and getting the idea that software was a thing a person could make.</p><p>The triumph of the nerds, in the way we usually talk about it, was about a specific window of time. The garage-to-industry arc. The rise of the personal computer as a mass-market product. That story is over. Woz retired years ago. Gates is philanthropy now. Kildall has been dead since 1994. The industry that grew out of what they built has consolidated into a handful of companies whose incentives look very different from theirs did.</p><p>But the ethos — the actual belief that made it happen — never really left. It just went quiet. It’s still there, in the small utilities being made by people who used them themselves. It’s there in the encrypted messaging apps and the local-first note-taking tools and the tiny paid Mac apps that don’t do analytics. It’s there in the fact that a person in Maseru can write an image converter and someone in San Francisco can find it and buy it and send an email about a bug, and the whole loop can happen without any company being involved except the App Store.</p><p>The triumph of the nerds didn’t end. It just stopped being the industry-defining story. It went back to being what it was in the beginning — a specific way of making things, for specific reasons, that a small number of people still care about.</p><p>I’m one of them.</p><p><a href="https://www.linkedin.com/in/thabo-david-klass/"><em>Thabo David Klass</em></a><em> is a software engineer in Maseru, Lesotho. He built </em><a href="https://apps.apple.com/us/app/senqu-image-converter/id6772722134"><em>Senqu Image Converter</em></a><em>, which is available on the Mac App Store.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4622aebc4002" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why App Privacy Matters Now More Than Ever]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/why-app-privacy-matters-now-more-than-ever-870345c4d882?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/870345c4d882</guid>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[data-privacy]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Sat, 25 Jul 2026 10:02:05 GMT</pubDate>
            <atom:updated>2026-07-25T10:45:21.672Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BdRKiLEZLjopmQvLlJk8qg.jpeg" /><figcaption>The Age of Surveillance Capitalism by Shoshana Zuboff.</figcaption></figure><p>A few weeks ago, <a href="https://sixcolors.com/post/2026/07/app-report-adding-a-shelf-to-my-mac/">Six Colors </a>— one of the most respected Apple-focused publications on the web — ran a mention of a small Mac utility I built called <a href="https://apps.apple.com/us/app/senqu-image-converter/id6772722134?mt=12">Senqu Image Converter</a>. It converts and compresses images. That’s it. JPEG, PNG, HEIC, TIFF, PDF. Everything happens on your Mac. Nothing gets uploaded anywhere.</p><p>The mention was small — one bullet in a roundup. But something about it kept coming up in conversations afterward, and I want to try to name what.</p><p>Think about the last three images you converted or compressed.</p><p>If you’re like most people, one of them was probably a screenshot of a meme, or a photo you wanted to send to a friend, or a picture for a blog post. Casual stuff. You didn’t think twice about which tool you used. You dragged it into a free web-based converter, maybe TinyPNG or Convertio or Squoosh, waited a couple of seconds, and downloaded the result.</p><p>But somewhere in your recent history, there was probably also this: a scan of a signed lease you needed to email to a letting agent. Or a photo of your child’s medical form before a school trip. Or an ID document a client asked for. Or a mortgage pre-approval letter with your salary on it.</p><p>Did you use the same converter for those?</p><p>Most people don’t. They pause. They open Preview instead, or they don’t convert the file at all and send it in whatever inconvenient format it was in. Not because they’ve read <a href="https://en.wikipedia.org/wiki/The_Age_of_Surveillance_Capitalism">Shoshana Zuboff on surveillance capitalism</a>, and not because they think TinyPNG is going to sell their data. Because it just feels wrong to upload that specific thing to a stranger’s server.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XDIfW_0Qt6zfBOh0Gh367A.jpeg" /><figcaption>The old worry about ‘Big Brother’ has a new name today: surveillance capitalism.</figcaption></figure><p>That instinct is the whole point.</p><p>There’s a version of the privacy conversation that treats it as a political value — an abstract concern about surveillance, big tech, corporate data collection. That conversation exists and matters, but it’s not really what most people feel most of the time. Most of the time we accept cookie banners without reading. We install apps that ask for excessive permissions. We paste stuff into ChatGPT that we probably shouldn’t.</p><p>But then there’s a specific file — a lease, a diagnosis, a photo of a kid — and the abstract question turns concrete. Suddenly you don’t want to click “I agree” on someone else’s terms of service. You don’t want to see “your file has been uploaded to our servers.” You don’t want to be one data breach away from your rental application appearing in a torrent somewhere.</p><p>This isn’t paranoia. It’s proportional. Some things belong to you in a way that other things don’t. And software should recognize the difference.</p><p>Most modern software doesn’t. The dominant model of the last decade is: everything is a service, every service runs in someone else’s cloud, and every file you touch is processed on hardware you don’t control by code you can’t see. This is fine — even good — for most of what most people do. Cloud photo backup is a genuinely useful invention. Collaborative documents are worth the trade-off. Streaming your music is fine.</p><p>But for the specific category of “files I actually care about,” it’s the wrong architecture. It asks you to trust a series of companies you have no relationship with, whose data retention policies you didn’t read, whose security postures you can’t audit, whose employees can theoretically see your file, and whose business models sometimes depend on knowing what’s inside it.</p><p>You don’t need to be a privacy zealot to opt out of that transaction for the important files. You just need to notice that the transaction is happening at all.</p><p>I built <a href="https://apps.apple.com/us/app/senqu-image-converter/id6772722134?mt=12">Senqu</a> because I wanted a tool that made the noticing unnecessary.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hO8dzUsF5P07kOPBUcDvgQ.png" /><figcaption><a href="https://apps.apple.com/us/app/senqu-image-converter/id6772722134?mt=12">Senqu Image Converter</a> running on macOS Tahoe 26.5.2</figcaption></figure><p>Senqu doesn’t upload anything. It has no accounts, no logins, no analytics, no telemetry, no third-party SDKs. It doesn’t connect to the internet at all — not to check for updates, not to phone home, not to sync preferences. When you drop a file into it, that file is decoded, processed, and re-encoded entirely by code running on your own Mac. Then the result lands wherever you told it to land. Then nothing else happens.</p><p>This is not a technical breakthrough. Every capability Senqu uses is provided by Apple’s built-in frameworks — <a href="https://developer.apple.com/documentation/imageio">ImageIO</a>, <a href="https://developer.apple.com/documentation/pdfkit">PDFKit</a>, <a href="https://developer.apple.com/swiftui/">SwiftUI</a>. The technology to do image conversion locally has been there for two decades. What’s unusual isn’t the how; it’s the fact that anyone bothered to build a utility that respects the boundary between “your Mac” and “someone else’s server” in 2026, when the default assumption is that every piece of software should route through the cloud.</p><p>The Six Colors review specifically called out one detail from a recent update: users can now drop files onto preset conversion targets, and conversion begins instantly, without needing to click a button. That change came from a user named Ron who emailed me feedback. Small friction, real fix. The reason I mention it isn’t the feature. It’s the loop: someone tried the app, told me what was annoying, I fixed it, and someone else — someone I’ve never met — noticed the fix. This is the way software used to work. It still can.</p><p>Here’s what I think has actually shifted recently, and why I titled this piece the way I did.</p><p>For most of the last decade, privacy conversations were dominated by big abstractions — surveillance capitalism, data brokers, the sinister-but-vague sense that “they” know too much. The specifics were mostly invisible. You worried about it in the same way you worry about climate change: real, important, and largely outside your daily agency.</p><p>But two things have changed the texture of it.</p><p>The first is that AI has made it obvious. Every service you use is now overtly training on the data it collects. What was once implicit — “we may share information with our partners” — is now explicit — “we use your interactions to improve our models.” The abstract concern has a concrete face. You know your files might end up in a training set. You know your writing might come back to someone else as an AI response. This makes it much harder to shrug off the abstract question.</p><p>The second is that data breaches have gotten routine, expensive, and personal. A quick look at the dark web monitor on your VPN is enough to demonstrate that nothing is secure anywhere but on your personal machine. Rental application databases have leaked. Medical imaging platforms have leaked. School records have leaked. If your file was uploaded, it was somewhere it could be stolen. And “we take security seriously” starts sounding hollow after the twentieth breach notification email.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ezSVF3MFFVr_voMKz3VD4w.png" /><figcaption>NordVPN with Dark Web Monitor feature on.</figcaption></figure><p>The result: people are increasingly making the noticing you had to make manually — “wait, do I want to upload this?” — into a default. And they’re looking for tools that let them not have to think about it.</p><p>Senqu is one such tool. It’s a small one, for a narrow purpose, at a small price ($4.99, one-time, no subscription). It won’t change your relationship with your data, but it will remove one specific place where you have to think about it. Convert your lease. Convert the medical scan. Convert the photo of your kid. Nothing leaves your Mac. Nothing gets logged. Nothing goes into anyone’s training set.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ymzeod44r847tUf8KYWWfg.png" /><figcaption>Senqu Image Converter in the <a href="https://apps.apple.com/nz/app/senqu-image-converter/id6772722134?mt=12">New Zealand AppStore</a>.</figcaption></figure><p>That’s not a privacy revolution. It’s just software behaving the way software should behave when the file matters to you.</p><p>I don’t think most people will ever articulate this as a principle. But I think many more people than we usually assume feel it, silently, every time they hesitate before dragging a sensitive file into a free web tool. That hesitation is a real signal. It deserves to be met with software that doesn’t require the hesitation in the first place.</p><p>That’s what I’ve tried to build. It’s a small thing. But it’s the small things that carry the most trust — because trust, in software as in life, is mostly earned in the small stuff first.</p><p><em>Senqu Image Converter is available on the </em><a href="https://apps.apple.com/hr/app/senqu-image-converter/id6772722134?mt=12"><em>Mac App Store</em></a><em> for $4.99. It runs entirely on your Mac. Nothing is uploaded. You can </em><a href="https://brettterpstra.com/2026/07/04/web-excursions-for-july-4th-2026/"><em>read another mention here</em></a><em>.</em></p><p><em>I’m Thabo Klass. I build software from Maseru, Lesotho, and I write occasionally on </em><a href="https://thabodavidnyakalloklass.medium.com/]"><em>Medium</em></a><em> and at </em><a href="https://badaboop.com/"><em>badaboop.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=870345c4d882" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From a Cold Email to Six Colors: What Happened After I Pitched Jason Snell]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/from-a-cold-email-to-six-colors-what-happened-after-i-pitched-jason-snell-35f289154651?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/35f289154651</guid>
            <category><![CDATA[swift]]></category>
            <category><![CDATA[macos]]></category>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[bootstrapping]]></category>
            <category><![CDATA[mac]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Sun, 19 Jul 2026 08:31:40 GMT</pubDate>
            <atom:updated>2026-07-19T08:31:40.984Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NuoMPG_i9xywGiCwB8VuOA.png" /><figcaption>Senqu Image Converter mention on <a href="https://sixcolors.com/post/2026/07/app-report-adding-a-shelf-to-my-mac/">SixColors</a>.</figcaption></figure><p>Six weeks ago, I sent <a href="https://sixcolors.com/jason//">Jason Snell</a> an email that I was pretty sure he would ignore.</p><p>He’d just published a piece on Six Colors called “Road to WWDC,” which included a section about the wave of AI-generated app pitches flooding his inbox — form-letter emails from developers who’d clearly used an LLM to write to him, promoting apps that had also probably been largely written by an LLM. He was probably fatigued. Understandable.</p><p>I write badly when I’m cold-emailing strangers. I don’t have a template. So I opened with that.</p><p>Here’s roughly what I wrote:</p><blockquote>Hi Jason,</blockquote><blockquote>I just read your “Road to WWDC” piece about the AI pitch flood. I’m one of the actual humans you mentioned, writing badly because I don’t have a template, from Maseru, Lesotho.</blockquote><blockquote>I shipped a small Mac app last week called Senqu Image Converter. It converts and compresses images on-device — JPEG, PNG, HEIC, TIFF, PDF. No uploads, no third-party SDKs. Built on ImageIO, PDFKit, SwiftUI, AppKit. $4.99.</blockquote><blockquote>I didn’t vibe-code it — wrote it the slow way over two weeks while job-searching. Not because vibe-coding is wrong (your piece is right that it’s lowering the bar in a useful way) but because I’m a developer by trade and writing Swift was the part I wanted to do — I enjoy the idea of having some control in my life and coding is that for me.</blockquote><blockquote>I don’t want to add to the pitch noise. If it’s interesting to you, here’s the App Store: <a href="https://apps.apple.com/hr/app/senqu-image-converter/id6772722134?mt=12">https://apps.apple.com/hr/app/senqu-image-converter/id6772722134?mt=12</a>. If not, no follow-up — and thanks for the years of Six Colors writing.</blockquote><blockquote>Thabo Klass</blockquote><blockquote>Maseru, LS</blockquote><blockquote><a href="http://badaboop.com/">badaboop.com</a></blockquote><p>That was the bet: that being an actual person with an actual story, sent from an actual place most tech writers (or people) rarely hear from, would cut through the noise better than any polished pitch could.</p><p>I didn’t hear back for weeks. Which was fine — I said no follow-up, and I meant it.</p><p>Then, this week, Philip Michaels — who’s writes for Six Colors alongside Jason — wrote back asking for a promo code. A few days later, the piece went up.</p><p>Senqu got its own bullet, alongside two other Mac utilities. What surprised me most wasn’t that the app got mentioned. It was what specifically got mentioned:</p><blockquote>Senqu Image Converter is a $5 image utility that lets you convert among JPEG, PNG, HEIC, TIFF and PDF files. The recent 1.2 update added the ability to drop images onto a preset in the full window for instant conversions, while dropping a file now immediately starts the conversion process using current settings.</blockquote><p>The 1.2 update. Not just the app — the specific thing that changed in the update.</p><p>That update exists because of feedback from a user named Ron Brinkmann. Ron used the app, hit exactly the workflow friction the Six Colors piece describes — having to open the app before you could drop files on it — and told me about it. He was right. It was annoying. I hadn’t noticed because I’d built the thing, and I was thinking about it as a builder rather than as someone actually trying to convert twenty images fast.</p><p>So 1.2 fixed it. You can now drop files onto preset drop zones for instant conversion using your current settings, or drop a file and have it start converting immediately. Small changes. Not obvious from the outside. But if you use the app every day, it turns Senqu from something you <em>use</em> into something you barely notice using — which is what you actually want from a utility.</p><p>And then Six Colors noticed the change. Not because I told them what to notice. Because Philip actually used the app.</p><p>That’s the whole indie-software loop working as intended: someone tries the app, tells you what’s annoying, you fix it, and eventually someone else — someone you’ve never met — notices the fix. It’s slow. It’s not viral. It’s not a growth hack. But it’s real.</p><p>I want to be honest about the numbers, because I think the honest version is more useful than the growth-hacker version: they are not that huge, YET.</p><p>I received an amazing mention from <a href="https://brettterpstra.com/">Brett Terpstra</a> and that gave Senqu the initial momentum that it currently has. The Six Colors mention might triple that this week. It might not. I don’t know yet. I’ll know in a few days.</p><p>What I do know is that every one of those sales came from someone reading something, somewhere, and deciding to give a $5 app from an unknown developer in Lesotho a try. Not from App Store search. Not from a viral tweet. From a person writing about it, and another person reading what they wrote, and making a small choice.</p><p>That’s the entire mechanism right now. It’s fragile. It also feels — in a way I didn’t expect when I started — like the way software used to work, before every app was a growth-loop machine.</p><p>If you’ve tried Senqu and it’s saved you time, the single thing that would help me most is not a share or a repost. It’s a rating on the App Store. Takes 10 seconds. Small utilities live or die by review count on the App Store, and I’m still building that base.</p><p>If you haven’t tried it, and you convert images even occasionally on your Mac, it’s $4.99 on the Mac App Store. Everything runs on your Mac. Nothing gets uploaded anywhere. No accounts, no tracking, no third-party SDKs.</p><ul><li><a href="https://apps.apple.com/hr/app/senqu-image-converter/id6772722134?mt=12">Senqu on the Mac App Store</a></li><li><a href="https://sixcolors.com/post/2026/07/app-report-adding-a-shelf-to-my-mac/">The Six Colors piece</a></li></ul><p>And thanks to Philip Michaels and Jason Snell for the coverage. And to Ron, <a href="https://brettterpstra.com/">Brett Terpstra</a> and everyone else who’s sent feedback that shaped where the app is now — 1.2 looks the way it does because of you.</p><p><em>I’m Thabo Klass. I build software from Maseru, Lesotho. If you want to follow along, I write on </em><a href="https://thabodavidnyakalloklass.medium.com/"><em>Medium</em></a><em> and post occasionally at </em><a href="https://badaboop.com/"><em>badaboop.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35f289154651" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The WebP gotcha that almost shipped: macOS reads WebP. It doesn’t write it.]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/the-webp-gotcha-that-almost-shipped-macos-reads-webp-it-doesnt-write-it-9f628c34a5b9?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f628c34a5b9</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[indiehackers]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Sat, 13 Jun 2026 08:39:26 GMT</pubDate>
            <atom:updated>2026-06-13T08:39:26.536Z</atom:updated>
            <content:encoded><![CDATA[<p>A small story from shipping <a href="https://apps.apple.com/sn/app/senqu-image-converter/id6772722134?mt=12">a Mac image converter to the App Store</a>, and a piece of ImageIO behavior I want more developers to know about, because if it had reached production it would have been an embarrassing day.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nJE1J27IUkRaieB-NJou5g.png" /><figcaption>Senqu Image Converter with problematic WebP option.</figcaption></figure><h3>The setup</h3><p>A week ago I shipped Senqu Image Converter to the Mac App Store. It’s a focused native Mac utility — you drag in images, pick a format, convert. JPEG, PNG, HEIC, TIFF, image-to-PDF. The full pitch is <a href="https://apps.apple.com/sn/app/senqu-image-converter/id6772722134?mt=12"><strong>on the App Store</strong></a> and in a <a href="https://thabodavidnyakalloklass.medium.com/i-got-tired-of-uploading-my-photos-to-random-websites-just-to-convert-them-so-i-built-a-native-mac-e21ae53d6fa7"><strong>separate launch article</strong></a>; this one is about a single bug I almost shipped, and what it taught me about ImageIO.</p><p>The format list in my app — the dropdown the user picks from to choose what they want their images converted <em>to</em> — initially included WebP. I’d added it because WebP is a real format that real users ask for, especially anyone working on web assets, where WebP often produces meaningfully smaller files than JPEG or PNG at comparable quality. I had it in the enum, in the picker, in the App Store listing’s keywords, in the App Store description. WebP was, on paper, a Senqu feature.</p><p>The problem is that on paper isn’t where software runs.</p><h3>The discovery</h3><p>During final pre-submission testing, I was clicking through every format combination — input format × output format × quality setting × resize behavior × EXIF stripping × menu bar vs full window mode. I do this every release because the testing matrix for a converter is shaped exactly like an opportunity to ship a silent bug.</p><p>I dragged in a folder of PNGs. Selected WebP as the output format. Clicked Convert. The progress bar moved. The “Done” state appeared. The savings readout showed something plausible.</p><p>But when I opened the output folder, the files weren’t there. Not corrupted, not zero-byte, not in the wrong place — just absent. The conversion had silently succeeded-failed: the app thought it had done the work, my UI thought everything was fine, and the actual writing of WebP bytes to disk had quietly not happened.</p><p>I went looking for why.</p><h3>The investigation</h3><p>My converter uses CGImageDestination from ImageIO, which is the standard Apple-blessed way to write image data on macOS. You create a destination with CGImageDestinationCreateWithURL, passing in a destination URL, a UTI for the target type, the number of images, and an options dictionary. You add the image. You call CGImageDestinationFinalize. Bytes hit disk.</p><p>The function that creates the destination is interesting in a particular way: if you pass a UTI that ImageIO doesn’t support as an output type, <strong>it doesn’t throw, doesn’t crash, doesn’t print to the console, doesn’t return nil in any way you’d notice without checking</strong>. Well — to be precise, it returns nil, but if you’re not asserting on that nil aggressively, you’ll see your converter “complete” with no errors and no output. The finalize call returns false. The file is never written.</p><p>So my next step was the obvious one: ask ImageIO what destination types it actually supports. The API for this is straightforward:</p><pre>let supportedTypes = CGImageDestinationCopyTypeIdentifiers() as? [String] ?? []<br>print(supportedTypes)</pre><p>The output, on macOS 26 (Tahoe) on Apple Silicon, looks something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eYSpQ6VrJLmOui0Evfd93w.png" /></figure><pre>public.jpeg<br>public.png<br>public.tiff<br>com.compuserve.gif<br>com.microsoft.bmp<br>com.adobe.photoshop-image<br>public.heic<br>public.heics<br>com.apple.icns<br>com.microsoft.ico<br>... plus a handful of RAW variants and proprietary Apple types</pre><p>What’s not in that list: org.webmproject.webp. WebP.</p><p>I tried a few obvious variations of the UTI string in case Apple had stashed it under a different identifier. public.webp. org.webmproject.webp. com.google.webp. None of them appeared in the supported destination type list.</p><p>I also checked CGImageSourceCopyTypeIdentifiers() — the <em>reader</em> side. That list does include WebP. macOS <em>can</em> read WebP via ImageIO; it has been able to since macOS 11 Big Sur, when Apple added system-wide WebP support. Preview can open WebP files. Quick Look previews them. Safari renders them. You can decode a WebP into a CGImage with no third-party library.</p><p>But you can’t write a WebP. ImageIO is read-only for that format, even four major macOS versions later.</p><p>This is what I want more Mac developers to know about: <strong>ImageIO’s reader and writer side are not symmetric, and the asymmetry isn’t documented prominently anywhere.</strong> You can assume reasonably that if macOS can open a format, it can save one. For WebP specifically, that assumption is wrong.</p><h3>Why does this asymmetry exist?</h3><p>I’m speculating now, because Apple doesn’t comment on the reasoning. But the speculation is informed:</p><p>WebP is a Google-developed format. Apple has had a historically complicated relationship with non-Apple-blessed image formats, and the long arc of Apple’s strategy has been to push HEIC as the cross-platform efficient image format of choice. HEIC has the property that Apple controls the technology stack (it’s based on HEVC, which Apple ships as part of the OS). WebP doesn’t have that property; Apple would be putting Google’s encoder into the system.</p><p>There’s also a licensing dimension. The reference WebP encoder (libwebp) is open-source under a BSD-style license, which is permissive enough that bundling it should be possible. But Apple’s bar for shipping third-party encoders in the system frameworks is high — they’ve historically preferred to either write their own implementation or wait. They wrote their own AVIF <em>decoder</em> but haven’t shipped an encoder. They added WebP <em>decode</em> via what appears to be a system-level integration, not via ImageIO’s full pipeline.</p><p>So the practical effect is: WebP gets read support via system integration (Preview, Safari, Quick Look, ImageIO’s reader side), but write support requires either Apple to ship libwebp in ImageIO or for individual apps to bundle their own copy of libwebp. The latter is what most professional image apps do — Pixelmator Pro, Affinity Photo, GIMP for Mac, they all ship their own libwebp encoder. They get WebP write support, but at the cost of pulling in a third-party dependency.</p><p>For a small indie utility, that’s a meaningful tradeoff. libwebp is well-maintained, but bundling it adds:</p><ul><li>A binary dependency that has to be cross-compiled for arm64 and x86_64</li><li>A code signing surface that has to be managed</li><li>Updates that have to be tracked when Google publishes libwebp releases</li><li>Sandbox/entitlement considerations</li><li>App Store review attention (third-party encoders sometimes draw extra scrutiny)</li><li>Possible patent encumbrance attestations, depending on how strict you want to be</li></ul><p>I’d built Senqu specifically on Apple’s frameworks — ImageIO, PDFKit, SwiftUI, AppKit — with zero third-party dependencies. That was an explicit positioning choice. The privacy story (“there’s no code in there that <em>could</em> exfiltrate your files”) relies on the absence of any third-party network code or SDKs, and that posture is much easier to maintain when the entire dependency graph is Apple frameworks. Adding libwebp just to enable one output format would have meant breaking the architecture for a single feature.</p><h3>The decision</h3><p>Here’s where I had to make an honest call.</p><p>Option 1: bundle libwebp, get real WebP support, ship it.</p><p>Option 2: pull WebP from the format list, from the description, from the keywords. Ship without it.</p><p>Option 3: leave WebP in the UI as a non-functional “coming soon” badge or similar.</p><p>Option 3 was a non-starter. Shipping a UI element that doesn’t work is exactly the kind of small dishonesty that erodes user trust. If WebP appears in the picker, it had better produce WebP files.</p><p>Option 1 was the right answer if I were optimizing purely for feature completeness. But I was a week from App Store submission, alone, and the prospect of adding a C library dependency and properly testing it across the build for x86_64 and arm64 — and re-justifying the privacy story now that there was third-party code in the dependency graph — was real engineering work that I’d already mentally not budgeted.</p><p>I chose Option 2. Pulled WebP from the format enum. Scrubbed it from the App Store listing’s description and keywords. Updated the screenshots so the format row didn’t show WebP. Wrote a “coming in v1.1” note for myself.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S3yd33D5kUHxnJQR9W4YYQ.png" /><figcaption><a href="https://apps.apple.com/sn/app/senqu-image-converter/id6772722134?mt=12">Senqu Image Converter with WebP removed.</a></figcaption></figure><p>The article-honest version of this is: I cut a feature because the cost of doing it right exceeded the cost of doing without it. That’s a small kind of engineering maturity, and a small kind of marketing maturity. Better to ship four formats that work than five formats where one silently fails.</p><h3>What I want indie Mac devs to take from this</h3><p><strong>Test every advertised format end to end, not just at the API call level.</strong> It is entirely possible for CGImageDestinationFinalize to return false and your converter to &quot;succeed&quot; in the user-facing UI because some intermediate state was happy. Always check that the output file exists, has nonzero size, and can be read back. I now have a test harness that does exactly this — for every output format the app exposes, it round-trips a known-good input image through the converter, verifies the output file exists, opens it back with ImageIO, and asserts the pixel data is recoverable. If that test had existed earlier in development, it would have caught the WebP problem on the day I added it.</p><p><strong>ImageIO’s reader/writer asymmetry is real.</strong> If you’re building anything that uses CGImageDestination, call CGImageDestinationCopyTypeIdentifiers() early in development and write down the list. Compare it to the formats your UI exposes. Don&#39;t assume that read support implies write support. WebP is the big one but it&#39;s not the only one.</p><p><strong>If you need an unsupported format, the choice is real and worth making consciously.</strong> Bundling libwebp or libavif is a legitimate path and many serious Mac image apps take it. But the cost should be weighed against your architectural commitments. For Senqu, the privacy story was load-bearing; the lone format wasn’t worth breaking the dependency graph. Your tradeoff might go the other way. The point is to make the tradeoff explicitly rather than have it caught at review.</p><p><strong>Apple may add WebP write support in a future macOS release.</strong> Or they may not. The current state has been stable across several macOS versions. Don’t bank on Apple solving this for you; if your app needs WebP write, decide now whether to bundle a library or skip the feature. The wait-and-see strategy will leave you in the same place a year from now.</p><h3>The honest small lesson</h3><p>A bug almost shipped because I trusted what an API name suggested rather than what the API actually returned. CGImageDestinationCreateWithURL sounds like it should work for any UTI. It mostly does. The cases where it doesn&#39;t are quiet and easy to miss.</p><p>The fix was a single afternoon of debugging and a few cuts to a feature list. The pre-fix cost — if I’d shipped it — would have been some number of confused users, possibly a one-star review or two, and the specific kind of indie-developer embarrassment where a thing in the picker doesn’t do the thing it’s labeled to do.</p><p>The post-fix state of the app is leaner and more honest. Four output formats. All of them tested. No silent failures.</p><p>Senqu Image Converter is on the Mac App Store if you want to see what shipped. WebP isn’t in there. Maybe one day, when I bundle libwebp for v1.x, it will be. For now, the version that exists is the version where every promised format works.</p><p>That’s the story. Now back to building.</p><p>If you’d like to try it out, Senqu Image Converter is available on the Mac App Store: <a href="https://apps.apple.com/sn/app/senqu-image-converter/id6772722134?mt=12"><strong>DOWNLOAD HERE.</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f628c34a5b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I got tired of uploading my photos to random websites just to convert them, so I built a native Mac…]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/i-got-tired-of-uploading-my-photos-to-random-websites-just-to-convert-them-so-i-built-a-native-mac-e21ae53d6fa7?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/e21ae53d6fa7</guid>
            <category><![CDATA[indiedev]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[mac]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Fri, 05 Jun 2026 20:12:07 GMT</pubDate>
            <atom:updated>2026-06-05T20:12:07.533Z</atom:updated>
            <content:encoded><![CDATA[<h3>I got tired of uploading my photos to random websites just to convert them, so I built a native Mac app that doesn’t</h3><p><em>The story of Senqu Image Converter — and why I think privacy belongs in boring tools too</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZaHZstn_FKZR_FSihBmj9g.png" /><figcaption>Senqu Converter, processing a batch on my Mac.</figcaption></figure><p>A few weeks ago I needed to convert about thirty HEIC photos to JPEG. Nothing dramatic — just everyday stuff. I opened my browser, hit one of those convert-online sites, and stopped before uploading.</p><p>These were personal photos. I didn’t know who ran the site. I didn’t know what they did with the files after the “conversion.” I closed the tab.</p><p>So I tried the desktop alternatives. Either bloated image editors where conversion is buried under five menus, or sketchy utilities that hadn’t been updated in years. None of them felt like what I actually wanted, which was something small, native, fast, and <em>private</em> — a tool that converts my images on my own Mac without phoning home or pretending to be a photo editor.</p><p>That night I started building Senqu.</p><h3>The thing the existing options miss</h3><p>There’s no shortage of image converters. Web tools like TinyPNG, CloudConvert, Squoosh. Desktop editors like Photoshop, Affinity, Pixelmator. They all “convert images.” But they fail in two specific, opposite ways.</p><p><strong>The web tools require you to upload your photos to a server.</strong> For a meme, fine. For your actual personal photos — receipts, screenshots of private messages, photos of your kids, anything sensitive — you’re handing your files to someone else’s infrastructure for a five-second job. Even if the site swears it deletes everything, you’re trusting strangers with your stuff to save thirty seconds.</p><p><strong>The desktop editors are overkill.</strong> I don’t need layers, filters, a tone curve, and a $20/month subscription to change a file format. I need to drag in an image, pick “JPEG,” and have it done.</p><p>There was an obvious gap in the middle: a focused native Mac utility that does <em>only</em> image conversion, doesn’t upload anything, doesn’t try to grow into a full editor, and respects your file the way a real tool should.</p><p>Senqu is that utility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kfmbp1g23Gbt-BDtWkgE6w.png" /><figcaption>Drag in a photo or a folder. Pick a format. Done.</figcaption></figure><h3>What it does</h3><p>The pitch is simple enough to fit in a sentence: drag images or a folder in, pick a format, and convert — everything happens on your Mac.</p><p>Under the hood it does five things well:</p><p><strong>Convert</strong> between JPEG, PNG, HEIC, and TIFF, or combine images into a PDF. Batch a whole folder; it handles hundreds of files without breaking a sweat.</p><p><strong>Compress</strong> with a quality slider, or set a target file size and let Senqu find the highest quality that fits under it. The size-savings readout shows you exactly how much space you saved.</p><p><strong>Resize</strong> to a maximum dimension when you need smaller outputs.</p><p><strong>Strip EXIF and GPS metadata</strong> so you don’t accidentally share where or how a photo was taken.</p><p>It also lives in your menu bar — a small dropdown panel for quick jobs — with a full window when you have a big batch.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nsz2YwJWqilvdeKjllx_tg.png" /><figcaption>Always a click away from your menu bar.</figcaption></figure><h3>Built on what’s already there</h3><p>The most important engineering decision I made was the boring one: <strong>use what Apple already ships.</strong> Senqu is built on ImageIO, PDFKit, SwiftUI, and AppKit. No third-party dependencies. No bundled libraries phoning home. No subscriptions to keep the lights on. The whole app is a few megabytes, runs on macOS 14 and later, and works completely offline.</p><p>This isn’t just an aesthetic choice — it’s how I get to credibly say “private.” When your app has no network code and no third-party SDKs, you’re not asking users to trust your <em>promises</em>; you’re shipping software that <em>can’t</em> leak their data even if I wanted it to. The privacy is structural, not policy.</p><h3>The thing I almost didn’t catch</h3><p>A few hours before submitting to the App Store, I was doing a final test pass. I clicked WebP as the output format. The UI said: <strong>“Not supported on this system.”</strong></p><p>Turns out macOS can <em>read</em> WebP files but doesn’t expose WebP as a writable output format through ImageIO — even on macOS 26 on Apple Silicon. My app had a runtime gate doing exactly the right thing (failing safely), but my App Store listing prominently advertised WebP as a supported format.</p><p>I almost shipped a listing that promised a feature my app couldn’t deliver.</p><p>I pulled WebP from the format picker, scrubbed it from the keywords, the description, the marketing copy, the support FAQ — everywhere. Re-archived, re-uploaded, re-submitted. The app and the listing now match.</p><p>I share this because I think it matters more than the technical detail: <strong>a tool that respects your privacy should respect your time and trust too.</strong> Advertising features that don’t work is a quiet form of disrespect. Catching that in testing, even though it meant another build cycle on a Sunday night, was non-negotiable. The whole pitch of Senqu is that it’s <em>honest</em> software. The listing has to be too.</p><h3>Where I’m from, and why the name</h3><p>I’m in Maseru, Lesotho. The Senqu — known downstream in South Africa as the Orange — is the river that rises in our highlands and flows across half the continent. It felt right to put a piece of where I’m from into something I’m making for the world.</p><p>The icon is a stylized river through mountains. If you ever wondered what the highlands look like, that’s the gesture.</p><h3>Where it is now</h3><p>Senqu Image Converter is available on the Mac App Store: <a href="https://apps.apple.com/sn/app/senqu-image-converter/id6772722134?mt=12"><strong>DOWNLOAD HERE.</strong></a></p><p>It’s $5.99, one-time purchase, no subscription, no tracking, no upsells. macOS 14 or later. If you ever wanted a small, focused, private image converter for your Mac — and you didn’t know exactly that’s what you wanted until you read this paragraph — I made it for you.</p><p>If you have questions, bug reports, or feature requests, the support page is here: <a href="https://badaboop.com/2026/05/25/senqu-image-converter-support/"><strong>https://badaboop.com/2026/05/25/senqu-image-converter-support/</strong></a>, and the privacy policy (short, because there’s nothing to disclose) is here: <a href="https://badaboop.com/2026/05/25/senqu-converter-privacy-policy/"><strong>https://badaboop.com/2026/05/25/senqu-converter-privacy-policy/</strong></a>.</p><p>Made in Maseru. Built honestly. Yours.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e21ae53d6fa7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Observer Effect and Multidimensional Simulation Theory: A Hypothetical Framework]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/the-observer-effect-and-multidimensional-simulation-theory-a-hypothetical-framework-b790982f7f53?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/b790982f7f53</guid>
            <category><![CDATA[simulation]]></category>
            <category><![CDATA[reality]]></category>
            <category><![CDATA[quantum-physics]]></category>
            <category><![CDATA[metaphysics]]></category>
            <category><![CDATA[philosophy]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Mon, 18 Nov 2024 04:58:15 GMT</pubDate>
            <atom:updated>2024-11-18T04:58:15.640Z</atom:updated>
            <content:encoded><![CDATA[<h4>Abstract</h4><p>This paper explores the intersection of quantum physics’ observer effect and a speculative multidimensional simulation framework. It posits a scenario in which human and/or all sentient beings are 4-dimensional (4D) projections of a higher-dimensional (5D+) entity or entities within a simulated reality. The simulation only stores state data, while 4D projections render their experience of reality through observation and interpretation. The paper discusses how this model could explain phenomena like the observer effect in quantum physics, suggesting that observation collapses stored probabilistic states into experiential reality.</p><h4>Introduction</h4><p>The observer effect in quantum physics states that the act of observing a quantum system alters its state. For example, the double-slit experiment reveals that particles such as electrons behave as waves until observed, at which point their behaviour becomes particle-like. This peculiar phenomenon has long intrigued scientists and philosophers, leading to questions about the nature of reality and consciousness.</p><p>Simulation theory offers a potential framework for understanding these phenomena. If reality is a simulated construct, the process of observation may involve rendering pre-stored states into experiential “realities.” In this paper, we explore a speculative framework where 4D humans are projections of 5D beings operating within a 4D simulation that stores only state data. Observation by these 4D projections could serve as the rendering mechanism, akin to a collapse of quantum probabilities.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CsKNHAqkLUlin5td_GIcEA.png" /></figure><h4>Multidimensional Framework of Reality</h4><p>5D Beings and 4D Projections</p><p>In this framework, a 5-dimensional being exists outside the constraints of linear time and space, encompassing all possible states and timelines. These beings create or inhabit a simulation structured as a 4D construct, wherein:</p><ol><li><strong>The Simulation:</strong> Stores all possible states as raw, probabilistic data.</li><li><strong>4D Projections (Humans):</strong> Render their experiential reality by observing and interacting with the simulation.</li></ol><p>The role of the 5D being might range from passive observer to active participant, possibly using the simulation to explore potentialities or enact a higher purpose.</p><p>Simulation as a State Storage Mechanism</p><p>The simulation is envisioned as a vast database containing every possible configuration of reality at each moment in 4D space-time. However, it does not directly generate the experience of reality. Instead, the 4D human projection acts as a rendering engine, translating probabilistic states into the rich, detailed experience we recognize as “life.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YUZO0-KUoPeZgiXxE50tJA.png" /></figure><h4>Observer Effect as Rendering Mechanism</h4><p>The observer effect in quantum physics could be interpreted as the act of rendering simulated states into a coherent reality. Before observation, a quantum system exists in a superposition of states, much like data stored in the simulation. Observation serves as a query that retrieves and collapses this data into a specific, rendered state.</p><p>Implications for Quantum Physics</p><ol><li><strong>Wave-Particle Duality:</strong> The dual nature of particles as both waves and particles could result from the simulation storing probabilistic states (waveforms) until observation renders them into discrete outcomes (particles).</li><li><strong>Non-Locality:</strong> Entangled particles might reflect the interconnectedness of stored states within the simulation, where observation in one location instantly updates the state globally.</li></ol><h4>Philosophical Implications</h4><p>This framework raises profound questions about the nature of reality, consciousness, and the role of the observer:</p><ol><li><strong>Consciousness as a Renderer:</strong> If humans are the “rendering engines,” consciousness might not only perceive reality but actively shape it.</li><li><strong>Free Will vs. Determinism:</strong> While the simulation may store all possible states, the choice of which state to render could involve a form of free will or influence from the 5D being.</li><li><strong>Purpose of the Simulation:</strong> The simulation could serve as a sandbox for exploring possibilities, learning, or artistic creation by the 5D entity.</li></ol><h4>Integration with the Observer Effect</h4><p>The observer effect might not be unique to quantum systems but a fundamental property of how the simulation operates. Without observation, the simulation remains in an unrendered state, conserving resources and allowing flexibility. Observation triggers the rendering process, collapsing potentialities into specific experiences.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4Lb4Y-YP51PIZntd5AgSbg.png" /></figure><h4>Visualization and Analogies</h4><p>To visualize this:</p><ol><li>Imagine a digital simulation where all possible game states are preloaded. Players (4D beings) navigate and render the world as they interact with it.</li><li>The 5D being is akin to the game developer, existing beyond the game’s constraints, influencing or observing how states unfold.</li></ol><h4>Conclusion</h4><p>The observer effect in quantum physics might reflect the mechanics of a multidimensional simulation. In this speculative framework, human beings are 4D projections of 5D entities, rendering stored states into experiential reality. This model bridges concepts from quantum physics, simulation theory, and philosophy, offering a fresh lens through which to view the mysteries of existence.</p><h4>Bibliography</h4><ol><li>Wheeler, J. A., &amp; Zurek, W. H. (1983). <em>Quantum Theory and Measurement</em>. Princeton University Press.</li><li>Bostrom, N. (2003). <em>Are You Living in a Computer Simulation?</em>. <em>Philosophical Quarterly, 53</em>(211), 243–255.</li><li>Susskind, L. (1995). <em>The World as a Hologram</em>. <em>Journal of Mathematical Physics, 36</em>(11), 6377–6396.</li><li>Chalmers, D. (1995). <em>Facing Up to the Problem of Consciousness</em>. <em>Journal of Consciousness Studies, 2</em>(3), 200–219.</li><li>Price, H. (1996). <em>Time’s Arrow and Archimedes’ Point</em>. Oxford University Press.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b790982f7f53" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Exploring the Top 10 Video Downloaders: Pros and Cons]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/exploring-the-top-10-video-downloaders-pros-and-cons-aa544801fa60?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/aa544801fa60</guid>
            <category><![CDATA[tik-tok]]></category>
            <category><![CDATA[videos]]></category>
            <category><![CDATA[youtube]]></category>
            <category><![CDATA[facebook]]></category>
            <category><![CDATA[download]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Tue, 09 Jan 2024 18:59:43 GMT</pubDate>
            <atom:updated>2024-01-09T19:08:21.628Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DsytyFnfxi602xW3kjdGWw.png" /><figcaption>Screenshot of popular service FDown (<a href="https://fdown.net/">https://fdown.net/</a>)</figcaption></figure><p>In today’s digital age, the ability to download videos from various platforms has become a sought-after convenience. Here’s a rundown of the top 10 video downloaders, each with its own set of advantages and limitations.</p><p><strong>Disclaimer:</strong> Video download services are intended for personal and non-commercial use only. Users should ensure they have the necessary rights or permissions to download and use copyrighted content. Downloading copyrighted material without proper authorization may infringe upon intellectual property rights. It’s crucial to respect copyright laws and terms of service of the platforms from which content is being downloaded. Users are encouraged to use these services responsibly and in accordance with legal regulations.</p><h4>1. YTD Video Downloader</h4><p><strong>Pros</strong>: Known for its user-friendly interface, YTD Video Downloader allows downloads from multiple websites. It offers a free version, making it accessible to a wide user base.</p><p><strong>Cons</strong>: The free version restricts simultaneous downloads, and users might encounter bundled software in the installer.</p><p><strong>Website</strong>: <a href="https://www.ytddownloader.com/">https://www.ytddownloader.com/</a></p><h4>2. SaveFrom.net</h4><p><strong>Pros</strong>: SaveFrom.net offers a user-friendly interface, simplifying the video downloading process for users of varying technical abilities. Its wide platform support, spanning major sites like YouTube, Facebook, Vimeo, and more, enhances its versatility. The availability of browser extensions further streamlines the downloading experience, allowing direct access from browsers like Chrome, Firefox, and Safari.</p><p><strong>Cons</strong>: However, the platform occasionally displays disruptive advertisements and pop-ups, potentially detracting from the overall user experience. Additionally, its functionality heavily relies on a stable internet connection, which, if unavailable, might hinder or pause the download process. Furthermore, compared to dedicated video downloader software, SaveFrom.net may lack certain advanced features like batch downloads or extensive file management options, potentially limiting users who seek more complex functionalities.</p><p><strong>Website</strong>: <a href="https://en.savefrom.net/">https://en.savefrom.net/</a></p><h4>3. RebelDowner</h4><p><strong>Pros</strong>: This has a niche user-based because of its support for only the Vimeo and DailyMotion platforms and doing it very well. Very clear and to-the-point usage, with no bells and whistles, and free as well.</p><p><strong>Cons</strong>: Despite it working very well, it only supports DailyMotion and Vimeo.</p><p><strong>Website</strong>: <a href="https://rebeldowner.com/">https://rebeldowner.com/</a></p><h4>4. ClipConverter.cc</h4><p><strong>Pros</strong>: ClipConverter.cc presents a versatile platform supporting various video platforms like YouTube, Vimeo, and Dailymotion, allowing users to download content from diverse sources. Its format and quality options offer flexibility, enabling users to tailor their downloads according to their preferences. Additionally, the availability of browser add-ons for Chrome, Firefox, and Safari facilitates convenient video downloads directly from the browser.</p><p><strong>Cons</strong>: However, users might encounter occasional disruptions due to ads and pop-ups on the website, potentially affecting the overall user experience. Moreover, ClipConverter.cc’s functionality heavily relies on a stable internet connection, which, if unstable or absent, might impede the download process. Despite its versatility, this platform might lack some advanced features found in dedicated video downloader software, such as batch downloads or extensive file management options, limiting users seeking more comprehensive functionalities.</p><p><strong>Website</strong>: <a href="https://www.clipconverter.cc/3/">https://www.clipconverter.cc/</a></p><h4>5. ClipGrab</h4><p><strong>Pros</strong>: ClipGrab supports various video formats and provides an integrated search function. Being free and open-source, it appeals to users seeking an accessible option.</p><p><strong>Cons</strong>: Some users report bugs, particularly on certain platforms, and it might lack advanced video editing features.</p><p>This is by no means an exhaustive list but provides some of the best in terms of user reviews. Take them for a spin and let me know what you think.</p><p><strong>Website</strong>: <a href="https://clipgrab.org/faqs/howto-download-youtube-video">https://clipgrab.org/faqs/howto-download-youtube-video</a></p><h4>6. FDown</h4><p><strong>Pros</strong>: This service focuses on downloading Facebook video and does it well.</p><p><strong>Cons</strong>: Despite great service, it is only focused on Facebook vide.</p><p><strong>Website</strong>: <a href="https://fdown.net/">https://fdown.net/</a></p><h4>7. WinX YouTube Downloader</h4><p><strong>Pros</strong>: Known for its speed and efficiency, WinX YouTube Downloader supports batch downloading and offers a straightforward interface.</p><p><strong>Cons</strong>: Its features are primarily focused on YouTube, and some users might find the software overly simplistic.</p><p><strong>Website</strong>: <a href="https://winx-youtube-downloader.en.uptodown.com/windows">https://winx-youtube-downloader.en.uptodown.com/windows</a></p><h4>8. aTube Catcher</h4><p><strong>Pros</strong>: This downloader offers not just downloads but also video conversion to various formats and includes a screen recorder. It’s free and relatively easy to use.</p><p><strong>Cons</strong>: Users might encounter ads while using aTube Catcher.</p><p><strong>Website</strong>: <a href="https://www.atube.me/">https://www.atube.me/</a></p><h4>9. Any Video Converter</h4><p><strong>Pros</strong>: Any Video Converter offers versatile features, including video conversion and downloading from various platforms. It’s available for free.</p><p><strong>Cons</strong>: The free version includes ads and bundled software.</p><p><strong>Website</strong>: <a href="https://www.any-video-converter.com/">https://www.any-video-converter.com/</a></p><h4>10. DVDFab Video Downloader</h4><p><strong>Pros</strong>: DVDFab Video Downloader supports a wide array of video sites and provides a streamlined downloading process.</p><p><strong>Cons</strong>: While the software offers a free trial, the full version requires a purchase.</p><p><strong>Website</strong>: <a href="https://www.dvdfab.cn/downloader.htm">https://www.dvdfab.cn/downloader.htm</a></p><p>This is in no way a comprehensive list — just some apps and services that have gotten great reviews from users. Give them a test run and let me know what you think!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=aa544801fa60" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Push notifications with Amazon’s AWS Simple Notifications Service (SNS) for Swift UI and iOS 16+]]></title>
            <link>https://thabodavidnyakalloklass.medium.com/push-notifications-with-amazons-aws-simple-notifications-service-sns-for-swift-ui-and-ios-16-6d0a0c49493e?source=rss-bf299d7ed1ac------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d0a0c49493e</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[swiftui]]></category>
            <category><![CDATA[push-notification]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Thabo David Klass]]></dc:creator>
            <pubDate>Mon, 06 Nov 2023 09:38:20 GMT</pubDate>
            <atom:updated>2023-11-06T12:18:47.124Z</atom:updated>
            <content:encoded><![CDATA[<h3>Push notifications with Amazon’s AWS Simple Notifications Service (SNS) for Swift UI and iOS 16+ in 2023</h3><p>It has been six years since the <a href="https://thabodavidnyakalloklass.medium.com/ios-push-with-amazons-aws-simple-notifications-service-sns-and-swift-made-easy-51d6c79bc206">original tutorial for push notifications with SNS</a> was published — a lot has happened since then. Swift UI has been released and we are now at iOS 17. Now more than ever, is it necessary to use push notifications to inform users and keep them engaged.</p><p>We have recently worked on a new app called <strong>BadaBoop</strong> — an AI-powered service used for the discovery, playback and chatting about music — through which we have learned all we needed to know to create an updated tutorial to enable AWS SNS push notifications for SwiftUI and iOS 16+. If you’re a music lover, please check out <strong>BadaBoop</strong> by following this link: <a href="https://apps.apple.com/us/app/badaboop/id6458538095?platform=iphone">CLICK HERE</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bYeAJI5gGwLPC9wkQ80n7w.png" /><figcaption>BadaBoop on the Apple App Store. For more, visit: <a href="https://badaboop.com/">https://badaboop.com/</a></figcaption></figure><h3>First Things First</h3><p>Let’s first create an <strong><em>Apple Push Sandbox Services </em></strong>certificate. This is a development certificate that helps you work with Apple push services when developing your app. Ultimately, when you are done with your development, you would create the <strong><em>Apple Push Services</em></strong> certificate meant for production in exactly the same way. For now, let’s work with the sandbox.</p><p>Open XCode and create a new SwiftUI app. Make sure to give it a unique bundle identifier.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TvoA4Q-jkaqRlEPZIjmIDQ.png" /><figcaption>Create a new SwiftUI app.</figcaption></figure><p>Log into your Apple developer account and go to <strong><em>Certificates, Identifiers and Profiles</em></strong>.</p><p><strong>Create an app ID.</strong> First click on the <strong><em>Identifiers</em></strong> menu item. Then click on <strong><em>Identifiers+</em></strong> to start creating a new app ID. Make sure that the <strong><em>App ID’s</em></strong> radio button is highlighted and then click the <strong><em>Continue</em></strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CbpxQsJFradIzsyYkAs94w.png" /></figure><p>Select the <strong><em>App</em></strong> type and click continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1aPM1Q2aqzsu9_l1NozYTg.png" /><figcaption>Select the App type.</figcaption></figure><p>Register the app by adding a description and using the same bundle ID you used when creating the app on XCode. Then click <strong><em>Continue</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hJ9VuEEdMUSOOJ1cEmvAqg.png" /><figcaption>Register the App ID.</figcaption></figure><p>Confirm that all the information is correct and then click the <strong><em>Register</em></strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*__tTQEKRlplnCXuvhyB7NA.png" /><figcaption>Rgister your app ID.</figcaption></figure><p>When you’re done creating the app ID, got to <strong><em>Certificates</em></strong> and click on <strong><em>Certificates+</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UgfFKCCAWZF6BIHeg-6rkg.png" /><figcaption>The Certificates, Identifiers and Profiles creation page.</figcaption></figure><p>Scroll down to the <strong><em>Services</em></strong> section and click on the <strong><em>Apple Push Notification service SSL (Sandbox)</em></strong> radio button and then click <strong><em>Continue</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kDiE4yWuDc9d0TgtVRLZgw.png" /><figcaption>Choose the Push Sandbox option.</figcaption></figure><p>In the <strong><em>Create a new Apple Push Notification service SSL (Sandbox)</em></strong> page, select the app ID you created from the dropdown and click continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ekqE_ZyiLpsD4g2ddTcMwg.png" /><figcaption>Create new Apple Push service (Sandbox)</figcaption></figure><p>Open Keychain Access on your computer and request a new certificate by click the <strong><em>Keychain Access &gt; Certificate Assistant &gt; Request a Certificate From a Certificate Authority…</em></strong> menu item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tK9hWWgW-_RnQp927WN8Rw.png" /><figcaption>Request a certificate.</figcaption></figure><p>Enter your user email, choose the <strong><em>Save to disk</em></strong> option and click <strong><em>Continue</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bRMLBYX9JkFqzmxoEzNRJg.png" /><figcaption>Certificate request.</figcaption></figure><p><strong><em>Save</em></strong> the certificate file in a safe location and the click <strong><em>Done</em></strong> when to finish the process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fOk09PqIsd00z35d7EJjkQ.png" /><figcaption>Save the certficate.</figcaption></figure><p>Go back to your Apple developer account and choose the certificate file you created and click Continue.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QjmEqVvKpjtEzmXU4RUMEA.png" /><figcaption>Choose the certificate file.</figcaption></figure><p><strong><em>Download</em></strong> you newly created Apple Push services certificate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZruTM4U5V1DqRK7gDa4Y5w.png" /></figure><p>Double click the newly downloaded file. You should see a new entry in <strong><em>Keychain Access</em></strong> under <strong><em>My Certificates</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CSqlm5JRNBLqVRm-VegnFQ.png" /><figcaption>New Apple Sandbox Push Services certificate com.badaboop.BadaPushTutorial.</figcaption></figure><p>Export the new certificate as a p12 by right clicking on it and exporting the certificate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i3wjIEvDx8GzVQ55vx3lCg.png" /><figcaption>Export your certificate as a p12.</figcaption></figure><p>Save it somewhere safe. You can give it a password or not — it’s up to you. This p12 will be used in AWS when you create a SNS application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Pi5XKlgFZltQdacyrVCYRA.png" /><figcaption>Save the p12 somewhere safe.</figcaption></figure><h3>Now, To The Real Work</h3><p><strong>Download the AWS iOS SDK</strong>: download the latest iOS by going to <a href="https://github.com/aws-amplify/aws-sdk-ios">https://github.com/aws-amplify/aws-sdk-ios</a> and downloading the latest SDK or alternatively, click this link <a href="https://releases.amplify.aws/aws-sdk-ios/latest/aws-ios-sdk.zip">HERE</a>.</p><p>This SDK, will be used to access AWS’s authentication and push notification services.</p><p><strong>Create a new AWS SNS platform application:</strong> log into you AWS account and navigate to SNS (Simple Notification Service). Under the <strong><em>Mobile</em></strong> section, click on the <strong><em>Push notifications</em></strong> menu item.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nMdoGnCRbf78Jsp1EPaBVQ.png" /><figcaption>The AWS SNS dashboard.</figcaption></figure><p>To create a new platform application, which will enable push notifications using SNS, click the <strong><em>Create platform application</em></strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DYHqrfzA_I3QEY5rHrx8bA.png" /><figcaption>List of platform applications.</figcaption></figure><p>On the <strong><em>Create platform application</em></strong> page, populate the <strong><em>Application name</em></strong> and set the <strong><em>Push notification platform</em></strong> as <strong>Apple iOS/VoIP/MacOS</strong>. Since we created a sandbox certificate, check <strong>Used for sandbox development</strong>. Set the <strong><em>Push service</em></strong> as <strong>iOS</strong> and the <strong><em>Authentication method</em></strong> as <strong>certificate</strong>. Choose the p12 file that you created earlier. If you gave it a password, enter the password as well — otherwise, leave it empty. When all of this is done, click the <strong><em>Load credentials from file</em></strong> button. Scroll to the bottom of the page and click the <strong><em>Create platform application</em></strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*c8pgh5sRDTPgFL0mgJMw7A.png" /><figcaption>Platform application creation.</figcaption></figure><p>A new platform application has been created. It contains an ARN (Amazon Resource Name) that will be used to send push notifications programmatically. So, please note your application’s ARN.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wIgTmCAVcDolwBH2PUqhPQ.png" /></figure><p><strong>Create an Identity and Role</strong>: we will now create a new identity and role that we will use to access AWS resources — in this case, AWS SNS. We will use AWS Cognito and IAM. Cognito is a service that provides application identity and authentication and IAM provisions access in every conceivable way to an AWS account.</p><p>It is important to understand that there are numerous ways to achieve what we are going to create in this step — this method just happens to be the easiest for our current task.</p><p>Open AWS in a new tab without closing the currently open SNS tab. Go to <strong><em>AWS Cognito</em></strong>. Open <strong><em>Identity Pools</em></strong> and click the <strong>Create identity pool</strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zWqfoGQ7nenbPMxJPib3lA.png" /><figcaption>AWS Cognito Identity Pools</figcaption></figure><p>In the <strong><em>Configure identity pool trust</em></strong> page, check <strong><em>Guest access</em></strong> and click <strong><em>Next</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O6h1S-MBxZ9HYyTqs9zUBQ.png" /><figcaption>Configure identity pool trust.</figcaption></figure><p>In the Configure permissions page, Create a new IAM role and enter your IAM tole name. You can make it something like <strong><em>&lt;app name&gt;-Unauthorized</em></strong> .</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d5UKGW7QzZ--mxQmfJACSw.png" /><figcaption>Configure permissions.</figcaption></figure><p>Enter the <strong><em>Identity pool name</em></strong> (this can be your app name) and click Next. Then click the <strong><em>Create identity pool</em></strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CYxv0OcF96Rwz4lERB09fg.png" /><figcaption>Configure properties.</figcaption></figure><p>Once the identity pool has been create, open it. Please note the <strong><em>Identity pool ID</em></strong>. This will help you retrieved tokens and configure access to resources for your app.</p><p><strong><em>Update IAM role:</em></strong> Open AWS in a new tab without closing the currently open Cognito tab. Go to <strong><em>AWS IAM</em></strong>. Open <strong><em>Roles </em></strong>and find your newly created role and open it. Click the <strong><em>Add permissions </em></strong>dropdown and choose<strong><em> Attach policies</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jB06TP-yBchkCRvqGETNAA.png" /><figcaption>IAM role.</figcaption></figure><p>On the <strong><em>Add permissions</em></strong> page, search for <strong><em>AmazonSNSFullAccess</em></strong>, check it and click <strong><em>Attach permissions</em></strong>.</p><p>We are now done with the AWS setup but don’t close those 3 tabs just yet.</p><p><strong>The fun begins:</strong> Lets start coding!</p><p>Go back to you XCode project and navigate to the <strong><em>General </em></strong>tab. Scroll down to the <strong><em>Frameworks, Libraries and Embedded Content</em></strong> section and click the <strong>+</strong> button. In the dialog’s dropdown, click <strong><em>Add Files…</em></strong> and navigate to the unzipped AWS iOS SDK you downloaded earlier. Add the following files (frameworks): <strong><em>AWSCognitoAuth.xcframework</em></strong>, <strong><em>AWSCognitoIdentityProvider.xcframework</em></strong>, <strong><em>AWSCognitoIdentityProviderASF.xcframework</em></strong>, <strong><em>AWSCore.xcframework</em></strong> and <strong><em>AWSSNS.xcframework</em></strong>. Make sure that you choose <strong><em>Embed &amp; Sign</em></strong> for all of them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Tp4tVpGWArYS5I1okZc2g.png" /><figcaption>Adding frameworks.</figcaption></figure><p>When this process is complete, your project should look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kyEpus8wPGAJJnK6no7KgQ.png" /><figcaption>After adding frameworks.</figcaption></figure><p>We now have to enable push notification capability for our app. Go to you project and click the <strong><em>Signing &amp; Capabilities</em></strong> tab. Click the <strong>+</strong> button directly beneath the tab. A capabilities dialog with open. Search for <strong>Push Notifications</strong> and pick it. Once that’s done, you should see two things: a newly added <strong><em>Push Notifications</em></strong> capability and a new entitlements file name <strong><em>&lt;AppName&gt;.entitlements</em></strong>. Your project should look something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xg4pC9x8GaKHA4mI-GqkWg.png" /></figure><p>Now that the project setup is complete, let is write some code. Open you app’s entry-point file <strong><em>&lt;AppName&gt;App.swift</em></strong>. Do the following things:</p><ol><li>Beneath the <strong><em>SwiftUI</em></strong> import, import <strong><em>AWSSNS</em></strong> and <strong><em>UserNotifications</em></strong>.</li></ol><pre>import AWSSNS<br>import UserNotifications</pre><p>2. Add a <strong><em>UIApplicationDelegateAdaptor</em></strong> to your main app struct. This is necessary so that you can use an AppDelegate that enables push notifications.</p><pre>@UIApplicationDelegateAdaptor private var appDelegate: AppDelegate</pre><p>3. Add an <strong><em>AppDelegate</em></strong> that enables notifications using SNS.</p><pre>class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate {<br><br>    /// The SNS Platform application ARN<br>    let SNSPlatformApplicationArn = &quot;Your SNS Application ARN&quot;<br><br>    var window: UIWindow?<br><br><br>    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool {<br>        /// Setup AWS Cognito credentials<br>        let credentialsProvider = AWSCognitoCredentialsProvider(<br>            regionType: AWSRegionType.USEast1, identityPoolId: &quot;Your identity pool ID&quot;)<br><br>        let defaultServiceConfiguration = AWSServiceConfiguration(<br>            region: AWSRegionType.USEast1, credentialsProvider: credentialsProvider)<br><br>        AWSServiceManager.default().defaultServiceConfiguration = defaultServiceConfiguration<br><br>        registerForPushNotifications(application: application)<br><br>        return true<br>    }<br><br><br>    func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {<br>        /// Attach the device token to the user defaults<br>        var token = &quot;&quot;<br>        for i in 0..&lt;deviceToken.count {<br>            token = token + String(format: &quot;%02.2hhx&quot;, arguments: [deviceToken[i]])<br>        }<br><br>        print(token)<br><br>        UserDefaults.standard.set(token, forKey: &quot;deviceTokenForSNS&quot;)<br><br>        /// Create a platform endpoint. In this case,  the endpoint is a<br>        /// device endpoint ARN<br>        let sns = AWSSNS.default()<br>        let request = AWSSNSCreatePlatformEndpointInput()<br>        request?.token = token<br>        request?.platformApplicationArn = SNSPlatformApplicationArn<br>        sns.createPlatformEndpoint(request!).continueWith(executor: AWSExecutor.mainThread(), block: { (task: AWSTask!) -&gt; AnyObject? in<br>            if task.error != nil {<br>                print(&quot;Error: \(String(describing: task.error))&quot;)<br>            } else {<br>                let createEndpointResponse = task.result! as AWSSNSCreateEndpointResponse<br><br>                if let endpointArnForSNS = createEndpointResponse.endpointArn {<br>                    print(&quot;endpointArn: \(endpointArnForSNS)&quot;)<br>                    UserDefaults.standard.set(endpointArnForSNS, forKey: &quot;endpointArnForSNS&quot;)<br>                }<br>            }<br><br>            return nil<br>        })<br>    }<br><br>    func application(_ application: UIApplication, didFailToRegisterForRemoteNotificationsWithError error: Error) {<br>        print(error.localizedDescription)<br>    }<br><br>    func registerForPushNotifications(application: UIApplication) {<br>        /// The notifications settings<br>        if #available(iOS 10.0, *) {<br>            UNUserNotificationCenter.current().delegate = self<br>            UNUserNotificationCenter.current().requestAuthorization(options: [.badge, .sound, .alert], completionHandler: {(granted, error) in<br>                if (granted)<br>                {<br>                    UIApplication.shared.registerForRemoteNotifications()<br>                }<br>                else{<br>                    //Do stuff if unsuccessful...<br>                }<br>            })<br>        } else {<br>            let settings = UIUserNotificationSettings(types: [UIUserNotificationType.alert, UIUserNotificationType.badge, UIUserNotificationType.sound], categories: nil)<br>            application.registerUserNotificationSettings(settings)<br>            application.registerForRemoteNotifications()<br>        }<br>    }<br><br>    // Called when a notification is delivered to a foreground app.<br>    @available(iOS 10.0, *)<br>    func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -&gt; Void) {<br>        print(&quot;User Info = &quot;,notification.request.content.userInfo)<br>        completionHandler([.alert, .badge, .sound])<br>    }<br><br>    // Called to let your app know which action was selected by the user for a given notification.<br>    @available(iOS 10.0, *)<br>    func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -&gt; Void) {<br>        print(&quot;User Info = &quot;,response.notification.request.content.userInfo)<br><br>        completionHandler()<br>    }<br>}</pre><p>So that in the end, your complete application code should look something like this:</p><pre>//<br>//  BadaPushTutorialApp.swift<br>//  BadaPushTutorial<br>//<br>//  Created by Thabo Klass on 05/11/2023.<br>//<br><br>import SwiftUI<br>import AWSSNS<br>import UserNotifications<br><br>@main<br>struct BadaPushTutorialApp: App {<br>    @UIApplicationDelegateAdaptor private var appDelegate: AppDelegate<br><br>    var body: some Scene {<br>        WindowGroup {<br>            ContentView()<br>        }<br>    }<br>}<br><br>class AppDelegate: UIResponder, UIApplicationDelegate, UNUserNotificationCenterDelegate {<br><br>    /// The SNS Platform application ARN<br>    let SNSPlatformApplicationArn = &quot;Your SNS Application ARN&quot;<br><br>    var window: UIWindow?<br><br><br>    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool {<br>        /// Setup AWS Cognito credentials<br>        let credentialsProvider = AWSCognitoCredentialsProvider(<br>            regionType: AWSRegionType.USEast1, identityPoolId: &quot;Your identity pool ID&quot;)<br><br>        let defaultServiceConfiguration = AWSServiceConfiguration(<br>            region: AWSRegionType.USEast1, credentialsProvider: credentialsProvider)<br><br>        AWSServiceManager.default().defaultServiceConfiguration = defaultServiceConfiguration<br><br>        registerForPushNotifications(application: application)<br><br>        return true<br>    }<br><br><br>    func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {<br>        /// Attach the device token to the user defaults<br>        var token = &quot;&quot;<br>        for i in 0..&lt;deviceToken.count {<br>            token = token + String(format: &quot;%02.2hhx&quot;, arguments: [deviceToken[i]])<br>        }<br><br>        print(token)<br><br>        UserDefaults.standard.set(token, forKey: &quot;deviceTokenForSNS&quot;)<br><br>        /// Create a platform endpoint. In this case,  the endpoint is a<br>        /// device endpoint ARN<br>        let sns = AWSSNS.default()<br>        let request = AWSSNSCreatePlatformEndpointInput()<br>        request?.token = token<br>        request?.platformApplicationArn = SNSPlatformApplicationArn<br>        sns.createPlatformEndpoint(request!).continueWith(executor: AWSExecutor.mainThread(), block: { (task: AWSTask!) -&gt; AnyObject? in<br>            if task.error != nil {<br>                print(&quot;Error: \(String(describing: task.error))&quot;)<br>            } else {<br>                let createEndpointResponse = task.result! as AWSSNSCreateEndpointResponse<br><br>                if let endpointArnForSNS = createEndpointResponse.endpointArn {<br>                    print(&quot;endpointArn: \(endpointArnForSNS)&quot;)<br>                    UserDefaults.standard.set(endpointArnForSNS, forKey: &quot;endpointArnForSNS&quot;)<br>                }<br>            }<br><br>            return nil<br>        })<br>    }<br><br>    func application(_ application: UIApplication, didFailToRegisterForRemoteNotificationsWithError error: Error) {<br>        print(error.localizedDescription)<br>    }<br><br>    func registerForPushNotifications(application: UIApplication) {<br>        /// The notifications settings<br>        if #available(iOS 10.0, *) {<br>            UNUserNotificationCenter.current().delegate = self<br>            UNUserNotificationCenter.current().requestAuthorization(options: [.badge, .sound, .alert], completionHandler: {(granted, error) in<br>                if (granted)<br>                {<br>                    UIApplication.shared.registerForRemoteNotifications()<br>                }<br>                else{<br>                    //Do stuff if unsuccessful...<br>                }<br>            })<br>        } else {<br>            let settings = UIUserNotificationSettings(types: [UIUserNotificationType.alert, UIUserNotificationType.badge, UIUserNotificationType.sound], categories: nil)<br>            application.registerUserNotificationSettings(settings)<br>            application.registerForRemoteNotifications()<br>        }<br>    }<br><br>    // Called when a notification is delivered to a foreground app.<br>    @available(iOS 10.0, *)<br>    func userNotificationCenter(_ center: UNUserNotificationCenter, willPresent notification: UNNotification, withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -&gt; Void) {<br>        print(&quot;User Info = &quot;,notification.request.content.userInfo)<br>        completionHandler([.alert, .badge, .sound])<br>    }<br><br>    // Called to let your app know which action was selected by the user for a given notification.<br>    @available(iOS 10.0, *)<br>    func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -&gt; Void) {<br>        print(&quot;User Info = &quot;,response.notification.request.content.userInfo)<br><br>        completionHandler()<br>    }<br>}</pre><p>Three very important things are happening in this code:</p><ol><li>We have a variable call <strong><em>SNSPlatformApplicationArn</em></strong>. The value of this variable is a string and is equal to the ARN of the SNS application you created earlier. Copy that string into your code.</li><li>Inside <strong><em>func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -&gt; Bool, </em></strong>we have to enter the identity pool ID. You can get this from the new identity pool you created in AWS Cognito. Copy the identity pool ID and paste it into your code.</li><li>We are also saving the retrieved <strong><em>deviceTokenForSNS</em></strong> and <strong><em>endpointArnForSNS</em></strong> in the UserDefaults. These two are important should you ever want to send a unique device a notification programmatically.</li></ol><p>Once all of the above is done, connect your iOS device to XCode and run your application on the device. A new endpoint will now appear in your SNS platform application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3uF-nmr7yr6XVNVtr8Bzuw.png" /><figcaption>New endpoint.</figcaption></figure><p>And now finally, you can send your new endpoint and push notification. First, click on the endpoint to open it. Click the <strong><em>Publish message</em></strong> button. Scroll down to <strong><em>Message body </em></strong>and type your message. Once done, click the <strong><em>Publish message</em></strong> button.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4c7uLUhv7eahTiR0IL4Hkg.png" /><figcaption>Message to be sent.</figcaption></figure><p>That’s it! You should receive a notification on the device that has your app. Congratulations, you now have a working example of SNS push notifications for SwiftUI on iOS 16+.</p><p><strong>Sending a message to a unique device programmatically:</strong> for this, we need the device token (<strong><em>deviceTokenForSNS</em></strong>) and the endpoint ARN (<strong><em>endpointArnForSNS</em></strong>). If we have these two bits of information, we can use the code below:</p><pre>if let deviceArn = userDict[&quot;endpointArnForSNS&quot;] as? String, let deviceTokenSNS = userDict[&quot;deviceTokenForSNS&quot;] as? String {<br><br>    /// Push notification meant for the spreebie uploader<br>    let sns = AWSSNS.default()<br>    let request = AWSSNSPublishInput()<br><br>    request?.messageStructure = &quot;json&quot;<br><br>    /// The payload<br>    let dict = [&quot;default&quot;: &quot;New direct message from BadaBoop.&quot;, &quot;APNS_SANDBOX&quot;: &quot;{\&quot;aps\&quot;:{\&quot;alert\&quot;: {\&quot;title\&quot;:\&quot;New message from BadaBoop \&quot;,\&quot;body\&quot;:\&quot;The BadaBoop music playback is great.\&quot;},\&quot;sound\&quot;:\&quot;default\&quot;,\&quot;badge\&quot;:1} }&quot;]<br><br>    do {<br>        let jsonData = try JSONSerialization.data(withJSONObject: dict, options: JSONSerialization.WritingOptions.prettyPrinted)<br>        request?.message = NSString(data: jsonData, encoding: String.Encoding.utf8.rawValue) as? String<br><br>        request?.targetArn = deviceArn<br><br>        sns.publish(request!).continueWith<br>        {<br>            (task) -&gt; AnyObject? in<br>            if task.error != nil<br>            {<br>                print(&quot;Error sending mesage: \(String(describing: task.error))&quot;)<br>            }<br>            else<br>            {<br>                print(&quot;Success sending message&quot;)<br>            }<br>            return nil<br>        }<br>    } catch {<br>        print(error)<br>    }<br>}</pre><p>Hope you enjoyed the tutorial. If you found this tutorial useful, please <a href="https://apps.apple.com/us/app/badaboop/id6458538095?platform=iphone"><strong>check out our app BadaBoop</strong></a> which uses the same lessons in this tutorial. Happy coding!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d0a0c49493e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>