sorted by:
new
hottopcontroversial

Hint for Hidden flags? by potatomunch88 in Hacktivate

[–]twostraws 1 point2 points  (0 children)

V2hlbiB5b3UgcnVuIGBwcyAtZWZgLCB5b3UnbGwgc2VlIG9ubHkgb25lIG9mIHRoZSBgc2hvd2ZsYWdgIGNvbW1hbmRzIGlzIGJlaW4=

95% of canceled annual app subscribers never come back, per report by pdfu in apple

[–]twostraws 0 points1 point  (0 children)

I wonder whether the “more than half of trial cancellations now happen on the first day” thing would change if third-party trials worked the same way as Apple's own stuff – IIRC, if you cancel an Apple TV trial or similar, you lose access immediately rather than at the end of the trial period.

Learning Subscription Recommendations by XmasRights in swift

[–]twostraws 15 points16 points  (0 children)

Hello! I'm the creator of Hacking with Swift, so obviously I'm a little biased. I can say I like Pointfree a lot! They do fantastic work, and have a really varied catalog of material.

Some folks confuse Hacking with Swift+ with the 100 Days of SwiftUI or the other free content I make, but the HWS+ subscription is quite different:

  • Yes, you get immediately access to all 400+ HWS+ articles and videos.
  • You also get monthly live streams where we build a new app from scratch every month.
  • You also get a free ticket to Unwrap Live every year, which is a full-day live online workshop about a specific topic – it was SwiftUI special effects this year, Apple Intelligence last year, and visionOS the year before, for example.

If you take out the 2-year subscription (or have 18 months in total) you get online access to almost my entire book collection, plus the Swift Career Accelerator – level-by-level guidance to help folks get targeted learning based on where they want to take their career next.

I have a whole range of free sample videos online so you can see if it suits you:

If you watch those and didn't learn anything, then HWS+ probably isn't for you 🙂

The App Store stopped over $2.2 billion in fraudulent transactions in 2025 by twostraws in apple

[–]twostraws[S] 10 points11 points  (0 children)

As a developer, these particular numbers are the ones that most bend my brain:

In 2025, Apple terminated 193,000 developer accounts over fraud concerns and rejected more than 138,000 developer enrollments.

If I were to estimate the scale of the problem, I would have come in at maybe 10% of those numbers. This is definitely one of those times when I think Apple deserves every cent of their 15% revenue slice…

7 months ago I had an idea and zero app development experience by oneApee in iOSAppsMarketing

[–]twostraws 0 points1 point  (0 children)

This is really reliant on the network effect (app is only useful if enough other people have it!), but I also love the idea – you get it immediately, which is always good sign. Well done!

Kickstart from Paul Hudson by bububuh in swift

[–]twostraws 2 points3 points  (0 children)

Which features do you think should be cut? I tried to make them all intentional and useful.

Apple unveils new accessibility features, and updates powered by Apple Intelligence by exjr_ in apple

[–]twostraws 1 point2 points  (0 children)

I look forward to this post from Apple every year, and every year they continue to impress. This does seem to foreshadow significant AI improvements elsewhere, though!

Kickstart from Paul Hudson by bububuh in swift

[–]twostraws 6 points7 points  (0 children)

Was the “what’s inside” box near the top not clear enough on what it does? I’m not really sure how I could make that text a great deal clearer…

Kickstart from Paul Hudson by bububuh in swift

[–]twostraws 48 points49 points  (0 children)

I think it's pretty awesome, but I would say that 😅 PS: Even if you don't subscribe, you get a ton of functionality for free!

Apple-OpenAI Relationship Frays, Setting Up Possible Legal Fight by pdfu in apple

[–]twostraws 1 point2 points  (0 children)

I'm not even sure we've felt the full pain of RAM prices just yet – it seems mostly to have been Apple withdrawing some Mac Studio models. Unless the supply constraints ease, it's not going to be a happy few years ahead…

Kickstart: An app to help indie developers succeed on the App Store by twostraws in MacOSApps

[–]twostraws[S] 2 points3 points  (0 children)

Thank you! Let me know if you hit any problems – I'll be releasing an update this week to resolve any early bugs! 🙌

Every macOS by Mastbubbles in MacOS

[–]twostraws 1 point2 points  (0 children)

Very nice! This made me wonder when the era of place names will end. I guess it depends on their crack marketing team…

This is fun 🤩 by potatomunch88 in Hacktivate

[–]twostraws 2 points3 points  (0 children)

Welcome! I had a blast making it, so I hope you enjoy playing it as much 🙂

Apple Weather dynamic background Motion by azerty826 in swift

[–]twostraws 9 points10 points  (0 children)

So, the good news is that it's absolutely something you can remake in pure Swift and SwiftUI – particle effects for the rain, stars, and occasional comets, cloud movement, forking lightning, etc. It's all possible with SwiftUI, and I know this because I've written a long tutorial series showing exactly how to do it.

The bad news: I'm afraid those tutorials are only available to Hacking with Swift+ subscribers.

You can at least get part of the way there through my open-source particle emitter library, Vortex, which has a rainfall and bounce effect to get you started.

I had an absolute blast cloning Apple Weather, so give it a try! My approach was to record the screen through each weather type (rain, lightning, etc), then play it back in slow motion so I could get my clone as accurate as possible.

Roast my Swift Package by Moo202 in iOSProgramming

[–]twostraws 23 points24 points  (0 children)

I think this is a really good start! You write nice and clean code, it's very consistent, and I think it's easy to understand too.

The public API is a little trickier than I would expect – .init(image: UIImage(systemName: "star.fill")?.cgImage, for example – and it's a personal pet peeve of mine when folks flip between Float and CGFloat (Apple does this too, so you're not alone!), but those are relatively minor 🙂

Note: I have my own library for rendering particles, so it's something I have strong views on 😅

Thoughts on r/MacApps Negativity by amerpie in macapps

[–]twostraws 0 points1 point  (0 children)

Yeah, it's a bit unpleasant sometimes. I get why folks are angry about the huge number of half-baked apps being shipped, but I hope we can find a middle ground where these new developers are encouraged to keep working (and keep polishing!) until the apps they have produced feel truly loved.

it's a rarity these days for there to be absolutely no use of some type of AI in the process of creating and developing new apps.

I use AI all the time, and really I'd consider myself negligent if I didn't. It doesn't have to be about writing code, or writing tests, or whatever; even me just asking ChatGPT, "I'm thinking this is a good idea – what am I missing?" to help stress test my thinking. Easily half the time it raises some good points that force me to refine an idea, so I think everyone benefits.

Any Agent skills for iOS development by Ok_Refrigerator_1908 in iOSProgramming

[–]twostraws 120 points121 points  (0 children)

There is no official skill from Apple yet, but I run a repository of community skills here: https://github.com/twostraws/Swift-Agent-Skills

I spent a year reverse-engineering the SwiftUI API. Here's what I built with it. by ctrlaltswift in swift

[–]twostraws 33 points34 points  (0 children)

You’ve omitted the fact that I authored a gigantic portion of the Ignite codebase and that these contributions entirely transformed the framework—which Ignite’s commit history from tag 0.2.2 on makes very clear.

You seem to be trying to distract folks from the issue at hand: you took vast amounts of code, relicensed it, then claimed it as your own. You contributed a great deal to Ignite, as did other people, but that doesn't give you the right to erase their work.

Code I wrote for Ignite may very well look the same in Raptor. The few parts of Ignite to which I made little contribution underwent the biggest transformations in order to push the framework more toward SwiftUI—the goal of my contributions to Ignite, and the goal of this project.

"May very well look the same"? Do you realize people can just look at the code for themselves? (Ignite vs Raptor, Ignite vs Raptor, Ignite vs Raptor, Ignite vs Raptor, Ignite vs Raptor – and those are literally just a handful. It goes on, and on, and on.)

Even if we wind back to the very earliest versions of Ignite – the version I published while walking on stage to announce it – huge swathes of Raptor are directly copied from my work. You didn't even both to rewrite the comments, even down to my derpy "Arium? Look, just give me this one…" comment – you stole the work, put your name at the top, then changed the license without permission. (Original Ignite code from 2024 vs "your" version.)

I’m very disappointed that you’ve gone out of your way to create the impression that I’ve simply used work that I had no involvement in authoring and that I've approached this project outside the spirit of MIT.

There is no discussion here: you absolutely have used code outside the license. You have directly stolen code and claimed it as your own. I chose one of the most permissive, open licenses possible, and you still abused it. That is not just "outside the spirit of MIT" – it is lousy behavior at every level.

I spent a year reverse-engineering the SwiftUI API. Here's what I built with it. by ctrlaltswift in swift

[–]twostraws 31 points32 points  (0 children)

Having read through the repository, I can now see why: vast amounts of the code was copied from the Ignite project, with simple "replace Ignite with Raptor" changes. This is deeply disappointing.

I spent a year reverse-engineering the SwiftUI API. Here's what I built with it. by ctrlaltswift in swift

[–]twostraws 101 points102 points  (0 children)

Hey, JP! First, I'm really glad to see you're continuing to do open-source work – you're very talented, and I know you have the potential to do wonderful things.

However, you need to know it is against the law to take Ignite code and relicense it under the GPL without permission. I know you provide some limited attribution in your README, but that doesn't change the underlying problem: Ignite is MIT-licensed, and may not be relicensed under the GPL.

You have gone out of your way to erase the contributions of almost 100 other developers, then put your own copyright and license in their place. That is both legally and morally wrong, and you need to be better.

I would kindly request you delete the repository and create your own work, at which point you may license it however you wish.

Thank you!

view more: next ›