11 years of iPhone images

Back in 2011 I started compiling short videos with all of the images that had been on my phone over the year. I did 2010 through to 2015 and then after that year I just never got around to compiling the following years. But with a welcome break over the holidays and 2020 over and done I finally made time to compile the missing years videos. In some of the previous years I’d made a custom audio track, but for these ones I just looked for suitable tracks amongst YouTube’s free audio, I think they work quite well though.

I’m tempted to make one massive video with 11 years of video but I think this may be a bit too long! :) Here’s all 11 videos so far:

iPhone view of 2020

iPhone view of 2019

iPhone view of 2018

iPhone view of 2017

iPhone view of 2016

iPhone view of 2015

iPhone view of 2014

iPhone view of 2013

iPhone view of 2012

iPhone view of 2011

iPhone view of 2010

How to fix – “LSLaunchProhibited Info.plist key is unsupported on Mac”

I don’t do a lot of iOS development but I do have a sticker pack and an app in the app store. I recently got an email from Apple developer support with the following message about my sticker pack:

Compatible iOS and iPadOS apps will automatically appear on the Mac App Store when the first Apple silicon Macs become available this year. However, we noticed the following issues with one or more of your apps that are opted in to appear.

The following apps will not be made available on Mac until a new version addressing these issues is submitted.

These apps contain the LSLaunchProhibited Info.plist key, which is unsupported on Mac:

I wasn’t quite sure what that meant and the email didn’t really give any indication as to how to fix it. A quick google search only came up with one single result, a forum post on Apple developer forums by someone trying to find an answer to the same question! :)

After having a quick look around in Xcode I *think* I’ve found the answer to the issue. Basically with the new Apple silicon Macs that have been announced it will be possible to run iOS apps on Mac and by default all iOS apps will be included in the Mac App Store. It is possible to specifically opt-out of having your app in the store but by default it will be included, so in this case the message relates to the fact that my sticker pack isn’t currently set to be available on Mac, only iPhone and iPad.

To resolve this you need to go to the sticker pack extension file of your Xcode project, under the “General” tab there should be a “Deployment Info” section. In there you can set whether it will work on iPhone and iPad, and if you’re running the latest version of Xcode there should also be a “Mac” checkbox. Checking that box will make the sticker pack available for Mac. Once that is done and a new build submitted to the app store this should then resolve this issue.

Playdate by Panic

Panic is a Mac and iOS software company whose software I’ve used myself or many years. Having followed them online through social media and their blog over the years they’ve always had a keen interest in gaming (one of my favourite posts was when they made 1980’s-esque fake packaging for some of their apps!).

In recent years they’ve moved into games publishing, “Firewatch” being the first title they supported and more recent the massively popular “Untitled Goose Game“.

Last year they announced an even bigger step into gaming with the announcement of their “Playdate” handheld gaming console. It might seem a bit crazy to try and launch an all-new hardware platform (never mind one with a hand crank as part of its UI!) but as in many things Panic does it seems there’s a method to their madness.

It’s due to launch sometime in (hopefully early) 2020, I’m looking forward to getting my hands on one of these. I’m a huge fan of Game Boy and retro tech so the aesthetics and design for the Playdate look pretty awesome to me!

Go read the full Playdate FAQ to get all the details about it. Also Edge magazine issue #333 has a great interview / sneak preview of it.

A Spacious place

I had a request the other day to find login details for the administrator of an old client website that we built for Dundee University in the earlier years of wideopenspace, the web design company I used to run. I hadn’t realised that the old client site was still up and running all this time after having been launched in 2006!

It was an amazing nostalgic blast-from-the-past to log in to the site’s control panel and see our custom-built content management system again! I’d kind of forgotten about the 100’s (actually, more like 1000’s!) of hours worth of time and effort that my business partner Andy and I put in to developing it and implementing it on client projects.

The CMS was called ‘Spacious’* and actually came in two versions, the full version with a multi-level navigation system and various custom modules and a ‘Spacious Lite’ version which was made for really small sites with single level navigation and also had access to certain modules.

Last logged in on 14/07/11, it had definitely been a while!

When we started development of our CMS around 2004 we hadn’t really used any third-party CMS platforms (WordPress V1 actually came out in 2004 but it wasn’t really on our radar). Instead we wanted to make something that suited our own specific purposes and client needs. So we didn’t really look at how any other CMS’s were doing things but in a kind of intentionally-naive way built it to work how we wanted it to work for the sites we were building for clients.

We used Spacious for a quite a lot of sites and we actually tried to secure funding to enable us to develop it into a fully fledged CMS product to sell to other companies, but sadly we never succeeded in getting funded. Eventually we stopped developing Spacious and as a company we increasingly moved our focus to WordPress as a platform around about 2009 (probably WordPress 2.7 I think?).

Client budgets were getting tighter and awareness of open source systems like WordPress was increasing. As such it was getting harder to sell clients a licence for a commercial CMS so financially the time spent building and maintaining our own one made less and less sense.

From a development perspective I found that WordPress had a lot of technical similarities to how we’d chosen to structure our CMS. Spacious had similar concepts of posts and pages, a plugin system offering various functions like Events, Email contact forms, Staff directories (‘modules’ in Spacious’ terminology), comments and even a form of multisite that could run more than one site from a single installation. (Spacious had some really cool features built into it that I’m pretty proud of in retrospect!)

From a client-facing perspective I liked the simplicity of WordPress, it was cognitively easy to use – especially compared to the complexities of something like Joomla at the time (I remember seeing all the steps that an incoming new client had to go through to edit their existing site in Joomla and it was extremely complex and confusing!).

As WordPress became our main focus the list of live client sites running Spacious grew shorter. So it’s very cool to see not just one but actually two sites that are still live and running on Spacious after all this time!


* Originally we wanted to call it ‘Fabric’ and trademark it but we weren’t successful – that’s a whole other story!

Descript Podcast Studio

This new podcast creation tool called “Descript” looks pretty amazing:

Descript builds simple and powerful collaborative tools for new media creators. We strive to eliminate the tedious work that often stands between an idea and its expression, so that creators can focus on developing their craft instead of their usage of tools.

https://www.descript.com

“Future Library” / “Framtidsbiblioteket”

I just came across this pretty incredible project called “Future Library” or “Framtidsbiblioteket”:

https://www.futurelibrary.no

Basically the plan is for one writer per year to write a book for 100 years, at the same time a purposefully-planted forest grows to maturity. After 100 years the trees will be harvested and then the still-unseen / unread books will be printed using the wood from the trees.

One thousand trees have been planted in Nordmarka, a forest just outside Oslo, which will supply paper for a special anthology of books to be printed in one hundred years time. Between now and then, one writer every year will contribute a text, with the writings held in trust, unpublished, until the year 2114. Tending the forest and ensuring its preservation for the one hundred year duration of the artwork finds a conceptual counterpoint in the invitation extended to each writer: to conceive and produce a work in the hopes of finding a receptive reader in an unknown future.

https://www.futurelibrary.no/#/the-artwork

It’s by a Scottish artist Katie Pierson who has also done some other interesting projects.

It’s an interesting idea to consider that these books might only be read by at least grandchildren if not great-grandchildren of any of us alive just now. It’s also made me ponder how the website for this project will be viewed in 100 years time – how well will this digital media stand the test of time?