Shout out to Nick last name withheld for doing the % math and letting us know that it should be 48% not 50% in their country. You are technically correct, and that is my favorite type of correct! Rounding down instead of rounding to nearest 5%, just for you. šŸ‘
Another big (pun intended) shout out to the tester running through the on-boarding process with huge ass fonts on a tiny ass phone. Definitely caught a couple places I screwed up.

Thank you UIScrollView for saving my bacon on this one.

I spend a large portion of my day zooming fonts in and out, really wish Apple had a reset to default option.

@paul thanks for doing the work! my eyes are getting worse and worse, and my font is getting larger and larger
@paul thoughts on why I get this error?
@nick i get this error too every time on gifs and videos….
@Arthur I run my own mastodon server and I was thinking the error is on my side of the house but I’m not seeing any setting that I haven’t properly enabled. Will likely look at logs today if I have time.
@Arthur as a follow-up I fixed this by installing ffmpeg onto my server and all is good. Might want to do the same if you run your own instance!
@nick I don’t run my own instance :( I wonder if the official app runs better than the TestFlight beta for gifs/videos?
@paul It’s so beautiful! I need it! 
@paul Do you think it makes sense to just host most views in scroll views? Certainly makes them easier to adapt for different screen and font size combinations.
@rhysmorgan pretty much, but for sure complicates other things.
@paul reset to default would be so handy
@dml can't tell you how many times I've gotten ā€œthat looks wrong" when showing a design implementation because the size is off one or two notches.
@paul i know the feeling! especially on small devices or if you have Larger Accessibility Sizes enabled …
@paul @dml You are not alone. iOS 16.3 at 135%
@paul šŸ¤” I think you could use Shortcuts to make a ā€œreset to defaultā€
@paul I'm about to make your day. Go into iOS accessibility settings, scroll all the way down and pick "per-app settings". Add Ivory as an app. Then you can go in and turn on larger text and it won't affect any other apps on your iPhone. Even better, there is a "reset font size to default' at the bottom. This is how I do my a11y testing of my apps on my iPhone now.
@MuseumShuffle this is all on the simulator though, I just want a menu option that does it.
@paul @MuseumShuffle Bug @parrots, wouldn't surprise me if he could add that to Sim Genie if it doesn't have it already
@paul @MuseumShuffle Not sure if helpful, but did you know that you can preview any SwiftUI View in all dynamic size-types?
@paul That would be nice. I focus on SwiftUI and the dynamic type variants in the SwiftUI previews drastically reduced my simulator usage for testing my a11y functionality.

@MuseumShuffle @paul But this isn’t a SwiftUI exclusive feature, right?

I assume it works with UIKit/AppKit views too, you just have to wrap them with a ViewRepresentable?

@JagCesar Honestly no clue. I'm beyond rusty with UIKit.
@MuseumShuffle @JagCesar yea this works, but can also have some strange side effects regarding autolayout and constraints.
@paul @MuseumShuffle The RocketSim šŸš€ app makes those sorts of things really easy on the simulator.
@paul is it worth my effort to pitch for the paywall and this screen to be combined into one long view? 😁
@rjj you can pitch and we might do it, but it’s not a do today thing.
@paul Smart man.
@rjj do send it in, if nothing else we did the $1.99 thing.

@paul super! Glad it was helpful. The counterintuitive thing about Monthly is LTV is usually higher than Annual! So while the money isn’t upfront, it’s not bad to encourage it at all.

Consider removing ā€œExample: ā€œ here and if I tap continue while empty, fill as mastodon.social

@paul It might save you X00 support tickets, tweets, and 1-star reviews if you special case this error, and show your own ā€œMastodon.Social is Overloading. Try again in 60 seconds.ā€ system alert back on the app UI that blames the right party. Or auto fire the FAQ.

@paul for paywall, it’s a new-ish pattern to have the features listed in long scroll view, behind a floating pay button.

Using the content you already have, you could likely put the translucent round rect poking up from button of the screen, and let the content flow under it? But that’s too semi-fancy.

The KISS way is one scroll view:

IMAGE
FLOATING ROUND RECT
FEATURE LIST

Prob +5% conversion rate alone?

@paul cc @mark Should be clear. If not I can draw it.

Some folks put ā€œNot Nowā€ in top right corner for this UX. I think you’d be okay with existing buttons though, since above the fold.

@rjj I'm going to let @mark look at all those. I just cook the pizza, he tells me where to put the ingredients.

We do show a section that let's you go the login help page when there's no login after bringing up the browser. Problem with being much more aggressive is that we can't really tell why it didn't login, server failure or user choosing cancel.

@paul Duh. Can’t believe I didn’t realize that. šŸ¤¦ā€ā™‚ļø

@mark moving the plans in the middle of first screen also let’s you list more features, cuz long is okay then. And a straight up list is actually a top 3 performing paywall layout. People just want a clear, concise list of the *limited features* they will/won’t get.

Replies
blurb

Post
blurb

Notifications
blurb

Themes
blurb

@rjj @paul Clear and thorough messaging around Mastodon server errors is going to be so crucial for third party apps. I think developers need to account for every action potentially failing.
@jsit @rjj yep, hard part with that is we'll only get a few for all the errors once we are out a while.
@rjj @paul feels like it'd be better as a list of top-10 instances as "Type in" at the end. Although might be considered too centralized by some, I guess.
@paul not big enough. need size 256

@paul

Might fix lower and upper end with

.dynamicTypeSize(.xSmall ... .xxxLarge)

@paul Way off the topic of zooming, but I love that elephant graphic.
@paul The accessibility inspector app has a screen for changing the font size with a button to restore defaults. It’s not as convenient as the options in Xcode but it’s better than nothing.
@paul When I get that view (and now that I’ve ā€œpaidā€ I can’t check it again), it it seemed like there was no way out of it except to follow the steps to subscribe. IIRC, even choosing to demo or whatever to not subscribe on the list screen didn’t seem to make it go away but I could be wrong about that part.
@paul love that ball compression.
@paul @jeff This happens to me too. I put the dynamic type control in my Control Center for quick access.
@paul thank you for doing this. We all need to optimize like this more. Sadly way too little of this in big corps.
@paul Not sure why double notifications happen

@gh0sti @paul not getting the double notifications here but Paul has talked about this before. Seems not on their end?

https://tapbots.social/@paul/109597709935158470

Paul Haddad (@[email protected])

Trying to track down an issue with folks getting dupe+ notifications. Got enough logs to conclude that the instance server is the one sending the extra pushes. Everything is E2E encrypted, so I can’t filter the pushes out on my server, it has no visibility as to what’s going through it. I can easily detect them client side but can’t filter them because of Apple API ā€œreasonsā€ (AKA people mis-using push). Maybe toggling the notification settings on dupe might clear it, but that’s really ugly.

tapbots.social
@Sonikku @paul I had it set to all but I’m going to try this and see if it keeps dupping
@paul Lol, I love that description. Getting the largest text to look right on an iPhone SE can be a challenge!

@MuseumShuffle @paul nice!

So when will you drop iOS15?

@paul Solution: only for iPhone Pro Max.
@paul šŸ‘‹ SE 2 here. The beta subscription screen looked a bit oversized. (Honestly, I’m used to designers forgetting this phone exists.)
@paul Apple should keep supporting the SE 1 form factor just to keep UI designers on their toes
@ezhik that's a bridge too far.
@paul I suppose small phones are not long for this world anyway šŸ˜”
@paul I have a 13 mini if that’s a data point you need. Looking forward to supporting you on release!