Snow Leopard

Snow Leopard
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.
Here’s a screenshot of me writing my last post in Slate 😜
I really wanted to add an image to the post, but I wanted more to write it using my own app.
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:
After I’ve done that, another build will be released!
👨🏻💻
Just spent a bit more time working on the structure of the compose view. It’s all nice and modular, and I’m very much enjoying developing it!
Here’s a little preview:
This should be an interesting read. 📖
Of course I’ve already got the new build, but then again I did just make it. 😜
I know I said the next build of Slate will be with composing, but I spotted a few bugs that I had to fix.
I’m uploading a build to TestFlight as I’m writing this. But who knows when it will actually go out. The beta review process seems longer than releasing to the store.
This post is to check the varying statuses of progress while posting something to your blog. When I wrote the first post, I actually received an error dialog on the screen, and that was just me doing something wrong with the response.
I’m going to either have to create a separate account for the Slate testing, or I’ll have to just come up with real posts that I can use while I’m working on the app.
Now for the second…
This is officially the first post from Slate for iOS.
It is also the first time the code to publish to a /micropub endpoint has been compiled, so that’s a double win.
Quick hack to make AirPods charge wirelessly. 😜
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.
As much as I find the constant emails from businesses, about the need to now opt-in to their newsletters because of GDPR super annoying. I’m very much looking forward to receiving a lot less emails. Because I haven’t opted-in to any of them.
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:
Slate is looking a bit nicer today! I’ve been adding a few extra images, doing minimal US localisation, and fixing a few things!
I’m now working on pagination, so that should be in the next version.
Here’s the favourite swipe action:
I really want to start working on the ability to compose posts in Slate, since it’s one of the last features before it’s functionally complete. However, there are a lot of mini tasks in my list as well. So I think the plan is to have the next version (v0.4) quite a small one, with bug features, design tweaks, etc. And then I can work on composing!
I’ve just come up with a safer way to sign up for the Slate beta. Here’s a simple form to submit your email, and i’ll add it to the list! blog.chrishannah.me/projects/…
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:
Feel free to get in touch about joining the beta, it’s compltely open to everyone.
Google Assistant is out there getting its hair cut, and booking restaurant reservations, while Siri isn’t allowes to turn the torch on. That’s a pretty bad sign of over controlling parenting.
Some more design work on Slate!
BBC:
Meet the robots that can pick and plant better than we can
My home screen is looking pretty good at the moment!