Sabitlenmiş Tweet
Flo writes Code
8.5K posts

Flo writes Code
@FloWritesCode
I've taught iOS development to 20,000+ people. Helping indies ship with https://t.co/JHegDygKkj
Germany Katılım Nisan 2021
714 Takip Edilen11.2K Takipçiler

Hey that’s me!
Nice of Apple to recognise the amazing folks from the iOS community 🙌🏾
developer.apple.com/community/reco…

English
Flo writes Code retweetledi

@athcanft Would love to hear your opinion apps.apple.com/de/app/mental-…
English

@CodeWithChris Lately Previews have stopped working for me, even in new projects. Perhaps my M1 Mac is getting a little old. But if they work, I always use them. Speeds up UI work tremendously.
English

@klemensstrasser Congrats & enjoy the rest of your vacation!
English

It is a really good problem to have - but I really can’t take a vacation without bringing a laptop 💻
(Deadline is last day of the vacation)
#indiedev

English

As the topic of SizeClasses came up in the comments, I made a full video covering the different options to write platform-specific SwiftUI: youtu.be/JEEWLOs4uY8

YouTube

Flo writes Code@FloWritesCode
Platform-specific code is important if your app supports multiple platforms (e.g. iPhone and iPad), but shares one UI codebase. I use the below approach for my iPhone + iPad + Mac project LaunchBuddy. The #if os(iOS) checks are needed, because UIDevice doesn't exist on macOS (if you aren't using Catalyst).
English

LaunchBuddy has become more intelligent!
The newest update brings app chat (with access to your app's tasks, releases, analytics, reviews & more), idea chat (to flesh out app ideas before working on them), turning reviews into backlog items, and much more.
@LaunchBuddy_App

English

@mykolaharmash Great stuff! I've used WhatsNewKit until now. Any chance you're planning to support the other platforms aside from iOS?
English

In addition to the video on AlignmentGuides, I'm also building a playground app to explore the API in practice.
Flo writes Code@FloWritesCode
Just from this piece of code, could you describe what is shown on screen? I always found "AlignmentGuides" super confusing. So I'm preparing a video on the topic now.
English

@alpennec This is exactly why I've been thinking about getting a Whoop for years. The screen on Apple Watch isn't what I use it for. The problem with Whoop is that I dislike the subscription-based pricing for a hardware product.
English

Another day, another screenshot iteration for LaunchBuddy.app
Light BG = Old
Dark BG = New
What do you think?


English

@ferga1ici0us Not sure what your question is, because these are computed properties.
English

Platform-specific code is important if your app supports multiple platforms (e.g. iPhone and iPad), but shares one UI codebase.
I use the below approach for my iPhone + iPad + Mac project LaunchBuddy.
The #if os(iOS) checks are needed, because UIDevice doesn't exist on macOS (if you aren't using Catalyst).

English

@mecid Depends on what you want to accomplish I'd say. For general layout things, sizeClasses are definitely the better option. But I e.g. want to add ScrollViews on iPads (both portrait and landscape), so the "CurrentDevice" implementation is perfect for that.
English













