Florian Mielke

It looks like @WorkTimesApp's subscription business is somewhat healthy overall.

However, the trial start rate could be higher.

Shout out to @RevenueCat for providing these valuable insights to us! 👏

Has anyone else noticed that iCloud’s spam detection has been off lately?

I’ve had a lot of legit emails from known senders going straight to spam.

Finally reached my goal for today! 🎉

Honestly, I'm surprised by how many extra steps it takes to get the default ci.yml of a new Rails project working. I need to document this for next time.

It might be, but I haven't seen it until now. 🫥

Wait, what? "Command" + "Click" on a localized string in Xcode takes you directly to the strings catalog entry. 🤯

I only knew the other way around. 🙈

I make products and help teams get better at it.

That's the essence of my 25+ year career.

Playing around with some logo ideas for my new product.

Does this look like a "Joe"?

Want a more productive development team?

Give them:
1. One, and only one, feature to build.
2. Uninterrupted time to build it.

That’s it.

Hello, good old friend. 👋

Let's see how far we get this time.

Finalized the first set of new App Store screenshots for WorkTimes in German and iPhone only–already live.

iPad and non-German screens will follow. But as Germany and the iPhone is about 95% of my user base, I've focused on the most important ones for now.

The screenshots of WorkTimes are visually outdated. So, in addition to overhauling the paywall, I also started working on new screenshots for the App Store.

They still need some final refinements, but I really like the new and fresh appeal and copywriting.

Left: old; Right: new

I completely redesigned WorkTimes' paywall, removing a lot of clutter and streamlining it. I'm quite happy with how it turned out.

No, 150-Year-Olds Aren't Collecting Social Security Benefits Elon Musk claims to have found rampant fraud in the Social Security Administration. There's a much simpler explanation.

Be aware of what you define as a reference date in your team if you can't or don't want to use "nil". 😉

Fun fact: I even learned COBOL during my studies back in 2001.

www.wired.com/story/elon-...

For the 15th time.

This must be my longest-running subscription.

I'm about to finalize the PDF export for WorkTimes.

I added some additional export options and a nice preview of the generated PDF file.

Don't waste time waiting for your computer to build or compile.

It is the main tool to do our work.

Buy the fastest machine you can afford.

Made great progress in converting a SwiftUI view into a multi-page PDF file.

How it started How it's going

Making progress on generating a PDF file with multiple pages from a SwiftUI view.

✓ It dynamically calculates the number of rows that fit on a page
✓ It renders a header on the first page

→ Next one: Render a footer on every page.

One of the most requested features for WorkTimes is to export your hours worked as a PDF.

Since iOS 16, we can generate a PDF directly from a SwiftUI view.

Unfortunately, it does not calculate page breaks and renders the view at its own or a given size.

Challenge accepted. 🫡

Neither does "architect".

MinuteTaker lets you link ongoing action items across meeting minutes, but seeing the big picture wasn’t easy.

The next update fixes that: You can now tap to view the full history of linked items in a clear timeline.

OpenAI and Softbank are starting a $500 billion AI data center company Nvidia, Microsoft, and Arm are among the technology partners.

Meanwhile in the EU... 😴

www.theverge.com/2025/1/21/2...

Premature optimization isn’t just wasted time—it can make your code harder to understand and maintain.

Aways remember: The cost of code is in the reading!

1️⃣ Make it work — focus on functionality, and surround it with tests.

2️⃣ Make it right — improve readability and maintainability.

3️⃣ If (and only if) performance issues arise:
• Measure
• Optimize
• Repeat as needed

In my career, I’ve seen countless developers fall into the trap of optimizing for performance too early.

Don't!

Don’t optimize upfront unless you can see AND measure real performance issues.

Instead:

Developers aim for that when creating pull requests, right?! 🫡

From my series of "Developer Happiness in Swift".

Here is another handy extension that saves me a lot of duplicated code.

No work today.

Instead, some family time.

But not without creating.

Have a lovely weekend.

Got some helpful feedback for the redesigned search bar in MinuteTaker.

I've refined the coloring and shadow to improve the contrast.

I must admit that Xcode's Predictive Code Completion is pretty helpful when writing Unit Tests.

Write the function name, and based on the context, it will give you a reasonable starting point.