This week's SwiftLee Weekly covers:

• App Store Optimization - Screenshots
• Observation in Swift deep dive
• Memory Integrity Enforcement

Enjoy this week's SwiftLee Weekly!

THIS WEEK'S BLOG POST

​Introducing Diagnostics: Improved Debugging and User Support​

If you've been reporting issues to me for RocketSim, you might have noticed the HTML attachment to your emails. Today, I'm telling you all about these reports and how they can streamline your app's support channel. This could be a way to reduce the number of times support reaches out to you as a developer 😉

SPONSORED

​Paywalls Made Easy​

Build and test paywalls with ease using RevenueCat's new native, remotely configurable paywall templates. Learn more here.

SWIFT EVOLUTION

An overview of last week's Swift Proposal state changes. Check them out when they're in review, as it's your opportunity to influence the direction of Swift's future.

WHAT I'M WORKING ON

App Store Optimization - Screenshots

After a busy post-holiday week, full of meetings (yes, even as an indie you have meetings, ha!), I'm finally back into work-mode. It was a fun week (even spoke with the Dutch radio on the new devices Apple announced), but structure is the key to success.

With OS launch day this week, I focused heavily on improving RocketSim's App Store presence. As a Mac-only app, a few different aspects apply, but these are general tips for other stores as well.

On Mac, your first screenshot is seen the most. It shows up in the search results, so it truly has to stand out. The second and third screenshots will show up when one visits the product detail page. Equally important!

This is how I started:

Not bad, you could say. Screenshots were already updated for macOS Tahoe, since I wanted to ensure my app went live before launch day. However:

• Nothing really stands out
• Copy is hard to read
• Images don't feel part of a consistent design

There wasn't a story behind it either. Well, there was—I was short on time.

It was time to go back to the drawing board, so I came up with a story for the screenshots:

• Screenshot 1: Build trust & authority
• Screenshot 2: Core Benefit (Aha moment)
• Screenshot 3: Breadth & add more trust

Altogether, this resulted in the following first three screenshots:

Much more consistency, clear copy, and a compelling story that should explain more iOS developers how much impact my developer tool can have.

I've also updated the remaining 7 screenshots, which I invite you to check out in the Mac App Store as the build is already live.

This section starts to become an article and you're right: this is worth an article. I'm actually measuring performance in an interesting manner, which I'll explain next week. Stay tuned!