Business

As a sort-of follow up to my post about Apple’s macOS Engineers running out of places to put new permission dialogs in, I had a thought, because, I do have those from time to time.

Here’s what’s up: In macOS, when you want to, for example, create a screenshot app and want it to be able to actually take screenshots, you’ll have to get permission from the user for it. With the upcoming macOS 15 Sequoia, that is going to be upped to two dialogs. One: the initial permission request, and two: a weekly reminder, asking if you want to continue to allow this app to capture your screen.
Here’s where my aforementioned thought comes in: Wouldn’t it be nice if a screenshot app from the Mac App Store was able to, like, take screenshots, right out of the box, without any permission dialogs?
I feel like apps on the Mac App Store should get some perks for being reviewed and vetted by Apple’s App Review.

So here’s my thought, wrapped into a couple of examples, to really drive my point home ad nauseam:
– A developer of a screenshot app that has successfully gone through App Review to be published on the Mac App Store should be able to request a default screen capture entitlement for it, which lets macOS know that no permission dialogs need to be presented, or asked for weekly, at all. It can just take screenshots right after download, because, you know, it’s a screenshot app, and that’s what the user downloaded it for.

– A developer of an audio recording app that has been reviewed by App Review to be released on the Mac App Store should be able to request a default Microphone recording entitlement, so it can record audio right after download, because, you know, it’s an audio recording app, and that’s what the user downloaded it for.

– A developer of an app that uses the user’s current location for core features that has successfully been reviewed by App Review to be released on the Mac App Store should be able to request a default Location entitlement so it can get its work done right after download, because that’s what the user downloaded it for.

Shouldn’t that be sort of the point of App Review?
I kind of understand making apps obtained from outside the Mac App Store jump through permission dialogs (to an extent, I just hate the new weekly permission reminders so much), but I feel like apps obtained from the Mac App Store could appear so much more user-friendly and polished without them, and would definitely make apps obtained from there feel special.

I guess what I’m saying is: Apple, please stop this Tour-de-farce security permission dialog onslaught and give users and developers some credit.


P.S.: I do realize it’s a pipe-dream. With all the ways stuff can be kept from App Review – which has happened time and time again – it’s not a system fit for such an implementation. Which, in turn, draws App Review’s reason for existing into question altogether.

Read more

Screenshot showing Yoink and its update-timestamp on the Mac App Store

7 months. I look in disbelief at the Mac App Store’s timestamp of Yoink’s last update, and I’m deeply embarrassed.
As a user, I’d think the app is abandoned. As its developer, I know that’s not true, because soon after I’d released v3.5.8 of Yoink for Mac, I began working on the next one:

Yoink for Mac's GIT commit messages, showing the date of the v3.5.8 commit and the date of when work on the next update began (3 days later)

The user, however, doesn’t know.

The situation isn’t any better for Yoink for iPad and iPhone, either, where the App Store states 5 months since the last update (v2.1.6).
Here, too, I began working on its subsequent update the day after submitting it to the App Store:

Screenshot of GIT commit messages of Yoink for iPad and iPhone, showing the date of v2.1.6, and when work on the next update began, a day later

I cringe even mentioning ScreenFloat (10 months), flickery (11 months), Glimpses (11 months), or Transloader (5! years!).

The problem, I think, is that I do not plan ahead much. I give my attention to the app that – in my view – currently needs it most (which has been mostly Yoink for Mac, and Yoink for iPad and iPhone lately), and whenever I feel the update is done (an arbitrary line I draw spontaneously most of the time), I release it and move on to the next app (or the same one again, if need be).

I want – and need – to do much better here.

So here’s how I’d like to improve:

  • Release what’s ready once a month
    If there have been changes made to apps and those changes are ready for prime-time, release the updates
  • Unless absolutely necessary, after an update, move on to the next app, not keep working on the one I just released an update for
    Aside from the positive effect of giving other apps the attention they need and deserve, it also reduces the possibility of me getting burnt-out working on the same app all the time
  • Be more vocal about what’s going on
    I should be more transparent about what I’ve been and am working on – it’s fun to share!

Here’s hoping. Thank you all for bearing with me 🙂

– Matthias
mail | website | twitter | instagram | facebook

Read more

Today, I released two quick updates to my apps Yoink for Mac and ScreenFloat. Here’s what’s changed.

Yoink for Mac v3.4.3

Yoink for Mac app icon

– Fixed a rare crash when trying to share files
– Fixes a bug where the keyboard shortcut would act up after deleting a file held by Yoink in Finder or using the app’s Share extension
– Fixed a bug where, after changing the screen’s resolution, Yoink would be misplaced

Links:

Yoink for Mac Website (with free, 15-day demo)
Yoink on the Mac App Store

ScreenFloat v1.5.15

ScreenFloat App Icon

– Fixes a rare crash when dragging the mini-icon of a floating shot


Links:

ScreenFloat Website (with free, 15-day demo)
ScreenFloat on the Mac App Store

Read more