April 12th, 2016
I’ve recently started dabbling with music again in my spare time. This is the first “finished” track with the new setup, that I’m reasonably happy with. Practice makes perfect, so more better stuff is on the way.
You can download a high quality MP3 version here on SoundCloud.
October 31st, 2015
cappchur has been designed to be simple and intuitive without any complicated set up process. Once you’ve installed the app you can start using it straight away, with no need to register up-front. You can also use it completely offline.
If you or someone you know is running a stall or exhibiting at an event please give our app a try and let us know what you think: cappchur.com.
July 4th, 2015
And this Twitch channel let’s you “live shout objects to dream about”.
And finally, these two videos are worth a watch:
Also, someone ran it on a clip from Fear and Loathing…
June 5th, 2015
Now this is a good idea. Presumably if it gains popularity Amazon will make moves to try to block it.
May 30th, 2015
Google’s new Photos app seems pretty great, with a consistent experience between the web and its native Android and iOS versions. The way your photos are organised is better than in Apple’s app, but the clincher is that they give you unlimited online storage if you’re willing to have them compress the originals. Given that (for me) this is just for family snaps, that is fine.
My iCloud storage has been full for weeks, and a combination of not being bothered enough to get round to it and not being sure I want to pay for the service (5GB feels tight, given I recently spent £ hundreds on a new iPhone) has led me to leave it like that. So goodbye iCloud Photo Library.
And as a it happens you can still post photos to iCloud shared libraries (which are, confusingly, separate from the iCloud Photo Library) direct from the Google Photos app.
Anyway two days into using it a couple of things are eluding me:
- A lot of people are tweeting about how impressive the facial recognition is, and the feature was demonstrated in the Google IO Keynote, but my Google Photos app (and also on the web) has no mention of faces anywhere and no apparent means of manually tagging faces – despite my library being full of photos of my family. Perhaps they’re rolling it out incrementally.
- Google has rather cleverly tagged and grouped a load of objects and things such as cats, cars, trains and food. However these collections contain some notable mistakes. A photo of one of my cats sleeping has appeared in the ‘food’ set, for example. Oddly there seems to be no way of untagging these things. Surely if you could then this could theoretically help its learning algorithm.
I’m guessing these things will be sorted out in due course, but there’s a chance I’m just missing something obvious. I’ve searched Google and Twitter but can’t find anyone else with the same problem (I mostly care about the face recognition).
May 21st, 2015
Back in 2010 Sir Tim Berners Lee warned about the threat posed to the web by Facebook et al.
Yesterday Jeremy Keith made this timely post (thanks to @fjordaan for tweeting it) about how poorly-performing websites are fuelling the shift towards native apps. In case you missed it, Facebook – which has already created a closed content silo – recently launched Instant Articles, which is basically their proprietary presentation mechanism for external content that is (presumably) be pre-cached to enhance the speed of the experience.
Rather than taking you to the external site they’re keeping you on Facebook, which is obviously good for Facebook, but you can’t argue with the fact that sometimes the user experience of external news sites is pretty terrible, so users will understandably like Instant Articles.
I’ll not repeat Jeremy’s points so read his post.
In a previous guise I remember arguing against going full-single-page-app in favour of ‘proper’ indexable content URLs on a project. And for keeping the number of requests on those pages down to a minimum (and, yes, making those requests super speedy via, minification, caching et cetera).
This is all well understood good practice, and yet a BuzzFeed article I just tested triggered 335 individual server requests. And one of the reasons I don’t like WordPress particularly is that out of the box (and with most of the popular themes) it leads to bloated request-heavy pages. There’s no culture of optimisation around it, yet WordPress seems more popular than ever (Yes, this site is WordPress; it’s good at doing blogs).
- It is only for use by logged-in users.
- It serves individual user-specific content such as their personal messages. It’s much faster to load the raw JSON data of a message than to reload an entirely new document with all its assets.
- It provides live status updates on some items.
- Our caching and local storage strategy ensures that users only load the application framework once, even though they may visit hundreds of pages within the app over the course of a week.
- And even then, our uncached page load is only 242KB (on a mobile device) and 18 requests, many of which are asynchronous.
It’s an application not a website, it just happens to use web technology. This is a very different use-case to a public page of content such as a news article.
The web is natively great at delivering pages of text very quickly. I consider documents and applications quite separately. And I don’t think it’s contradictory to be a cheerleader for both. The trick is, I believe, not to try to make documents more application-like.
This article on A List Apart also makes some good points