A short update regarding my earlier piece on Apple blocking Steam’s Steam Link app.

Turns out I was correct in that the type of app has nothing to do with the rejection. Which is why the appeal to Apple about there already being other remote-desktop style apps, didn’t work.

However, Reuters wrote a great piece, including quotes from Valve. The major point is this:

Steam, however, also offers purchases within games distributed through its platform and also takes a cut of those purchases. Apple’s App Store guidelines ban such a store-within-a-store unless the purchases flow the Apple’s infrastructure and pay Apple’s cut.

That is why it was rejected.

It’s also the reason why you have a Kindle app on iOS, but have to go to the Amazon website to purchase books. Because they don’t want to share any revenue with Apple.

It may seem terrible that Apple demand a cut of all purchases made on their platform. But they are the ones supplying the platform, and the opportunity for developers to build apps for them.

At first glance, Apple rejecting Valve’s Steam Link seems like a bad idea.

However, I haven’t yet seen anyone with details about why it was rejected. I’ve seen “business conflicts” mentioned, however I can’t pay too much importance to any of the reports until I see at least the guideline that it didn’t follow.

If it does indeed break an app review rule, then you can’t really argue that it was rejected. But if, like many articles pointed out, there are other remote-desktop style apps already in the app store, and Steam Link is essentially just that, then these should receive the same treatment.

To counter that point, there is also the fact that we do not know the reason why it was rejected. Which means the reason could be nothing to do with the fact that it’s a remote-desktop app.

Also, approving and rejecting is a bit of a dick move. But more likely caused by human error.

I recently started working on one of the most important parts of Slate, composing and publishing posts.

It was maybe the only feature I actually planned out, and I have a whole section in Things dedicated to it. I already know what features I want to add before I can say it’s complete, but I think I will also release a beta version for this feature, as soon as the minimal tasks are completed.

At the moment, it’s quite basic in functionality. It accepts an optional title, and of course the list content. No replies, image uploading, etc.

The first step was, of course, to add the code to actually post something to Micro.blog. But since then I’ve just been working on the UI.

Again, that is quite simple. There’s a field with for the title, a much larger text field which is where I’m currently writing this post content, and also a character count in the bottom-right corner.

Before releasing a beta version of composing, there are just a few things I want to add:

• Markdown highlighting.
• Easy way to insert Markdown syntax, such as links, or italics.
• Replying to a post.
• Replying to a user straight from their profile.

After I’ve done that, another build will be released!

👨🏻‍💻

Although I’m not thinking it about it too much right now, I’m not completely sure how Slate will be monetised in the future.

I would like to offer Slate as a free app, like Icro.

My first idea is to put a “Tip Jar” style feature in Slate after it is released. And then maybe it can be paid in the future? I’m not sure about how well that would be received though.

For now, I’ve set up a “Buy me a coffee” page, as I thought that was a simpler solution right now. I’m not trying to use this to request anything, but it’s just out there as a way to support the development.

www.buymeacoffee.com/jU2craD

I’ve done enough for v0.4 of Slate I think, so I’ll upload that to TestFlight now. And then I can start working composing for v0.5!

Here’s the raw release notes:

• The vertical spacing in the post cell, and also separating them has been adjusted.
• Names are now slightly bold, with the username being less distinguished.
• Inline images now load for urls with https.
• Fix scenario where login fields would not adapt properly to the keyboard height.
• If you view your own profile/author view, it will hide the follow button.
• Inline images are resized vertically, if they are in landscape orientation. However they will not be resized vertically as that could lead to a very bad reading experience.
• Tapping anywhere on a cell for an author will now open their profile.
• The Favourite and Conversation swipe actions now have images.
• Started localising the text for US english.
• Fixed relative dates being completely inaccurate!

Feel free to sign up to the beta.

It’s time for me to push another beta version of Slate!

Honestly, I didn’t complete everything in my plan for this version. But versions don’t really mean anything at the minute, as it’s probably better for the whole process if I just release more often.

Here’s the raw release notes for this build:

• Added pull to refresh on the profile and author views.
• Profiles and author views now have the name as the title.
• Times on posts are now relative.
• Links are no longer underlined.
• Instead of verifying the app token every time the app is launched, it moves straight to the timeline, and checks in the background.
• There are now no separators in the post tables.
• The light theme is slightly lighter.
• The menu adapts to the theme as well now.
• Fixed the issue where some tables were not getting their background colour changed when a new theme is selected.
• Line height is now slightly bigger.
• You favourite posts now by swiping from left -> right.

Feel free to get in touch about joining the beta, it’s compltely open to everyone.