Uvildy road in the fall
Yesterday I was driving from Uvildy back to Chelyabinsk. Here is the beauty of the fall for you:
I’m very impressed by Instagrams’s Hyperlapse video stabilization. This place on the map.
See also: Uvildy ice.
Yesterday I was driving from Uvildy back to Chelyabinsk. Here is the beauty of the fall for you:
I’m very impressed by Instagrams’s Hyperlapse video stabilization. This place on the map.
See also: Uvildy ice.
John Gruber compares iPhone and Apple Watch introductions in Episode 14 of Electric Shadow podcast (starting at around 1h 24m mark):
I think that the best was the 2007 Macworld expo keynote introducing the iPhone. Let’s see where they go with the watch, but I think even in the most optimistic scenario the watch doesn’t change everything the way the iPhone did.
The iPhone was pulled out of thin air. I think to this day — now we are 7,5 years after that — it was absolutely five years ahead of its time, maybe more. I think maybe if Apple had never released it, the phones we would have been using in 2012, five years later still wouldn’t have been like that. It was impossible. It really is just what it seemed like.
I don’t think they needed a good event, I think they could have had a shitty event to announce it, and if they released the exact same phone seven months later, it would have been fine. It would eventually, with the years, work out.
The advantage of having a perfect event to announce it though was that for the people who opened their minds and just paid attention to it, it gave us a head start as to just what it was that we’ve seen. Half of the people who were paying attention came out that event understanding: Wow. This is amazing. The entire tech world has just changed. And then the other half were, like, this is ridiculous, the thing doesn’t even have a keyboard, no one’s gonna buy it. But if you paid attention, the fact that the event was so perfect, it gave you the context to understand something without ever actually even getting to use the device.
Agreed.
When Apple revealed Apple Pay, they first showed it on an iPhone with Touch ID and later mentioned that it would also work with the Apple Watch. But how does Apple Watch know that you are you without Touch ID?
Here is an idea.
Apple Watch requires the iPhone. It would make sense if Apple Pay on the Watch required the iPhone with Apple Pay support. The only such phones are the 6 and the 6 Plus. Both have Touch ID.
Apple Watch can tell if someone is wearing it using its heartbeat sensor. When no one is wearing the watch, it will not work with Apple Pay. When you put the watch on, it will still not work with Apple Pay, as it does not know who is wearing it. As soon as you use Touch ID for the first time to unlock your phone in a close proximity, the Watch will enter a “secure state”: now it knows that it is put on your hand. From that moment Apple Pay will work until you take the Watch off or the phone gets too far away from it.
The chance that you are trying to buy something before you’ve unlocked your phone for the first time during a day is almost zero. And in this rare case the Watch can just ask you politely to confirm the payment with Touch ID.
The new version of Ångström codenamed Greenwich is now available. Everyone can now convert hours to seconds, weeks to minutes etc. Paid users also get timezone conversion:
What time is in New York when it’s five o’clock in London? Now it is as easy as typing “5lo”. We know when and where daylight savings time is in effect.
Also, we’ve finally done the rounded corners right:
Ah, so much better now! It took effort on Alex’s side to make this work fast and reliably on all supported devices.
We’ve added more currency symbols, including Turkish lira, Cambodian riel and Armenian dram (by the way, we’ve always had Bitcoin):
And finally, we do a little bit better job explaining what you get with an In-App Purchase. Instead of listing unit symbols, we spell out the whole names.
Thanks to Federico Viticci of Macstories for a great recent review:
The result is an incredibly fast conversion process that only takes a few taps and doesn’t require you to scroll long lists or bookmark favorites for quick access. For me, typical usage of Ångström goes like this: I open the app, type a number, insert the first letter of a unit, and I’m done.
If you are not yet using Ångström, you should:
Download in the App Store for free
Stay tuned.
When you cancel a Time Machine backup, it takes some time to stop:
Actions of programs have no inertia, they can be stopped immediately. If stopping something would leave a system in an inconsistent state, and you need to clean things up first, that’s what the user interface should say. But “Stopping” makes no sense. Just stop.
This problem is not uncommon, and I was thinking about writing a post about it for some time. But here is what happened recently. Mail in Yosemite Beta had already been “Disabling” my account by “Closing” something for several minutes, so I decided to cancel it — and got this:
I had to force quit it after a couple of minutes.
Added in August, 2016: And here, Dropbox is “Pausing”:
Here is my new morning psytrance / full on mix, Crystal Smile:
The tracklist is:
Good morning.
Form labels should be put on a baseline of their fields’ text:
If you put a label at the vertical center of a field, as some do, it will jump up when split into lines:
It gets worse with more lines; here the long label has actually shifted down the field:
If labels and fields behave this way, a form looks unstable and loosely built, and you start thinking badly of its developer.
The first line of a label text should always stand still:
Same with multiline fields’ text:
A form is an editable table, so the table layout principles apply.
One of the objectives of the design of Ångström was getting the result as fast as possible. But we’ve confronted a problem with currencies: getting the current rates takes time.
We didn’t want to give up on immediate feedback. So we decided to show the result with the rates we have locally and use an approximate equality sign to hint at it:
While the currency rates were updated, a standard spinner spun in the phone’s statusbar. When the new rates were downloaded, we updated the result and replaced the sign with the strict equality one.
And then an idea came to our minds to make the process more fun: instead of showing a boring spinner, we have animated our equality sign. The wave oscillates during update, and when the data is loaded, its amplitude gradually decreases to zero:
This is how it shipped.
We like it how one element performs two functions: shows that the data is approximate and shows that the new data is coming. You don’t see this in the app often, as we periodically update the rates in the background, but it still appears sometimes if you are lucky.
A website menu item has three possible states.
Unselected:
We are not at “Swag” and can go there by clicking. The link is underlined, on hover it highlights and the cursor changes to a pointer, the link leads to the main page of the section.
Current:
We are at the main page of the “Swag” section. The text is put on a background, does not react in any way to hover or clicks.
Parent:
We are at one of the pages of the “Swag” section, but not on the main one. The link is put on a background and underlined, on hover it highlights and the cursor changes to a pointer, the link leads to the main page of the section.
This is an obvious and logical standard. Highlighting the current section with an underline or reloading on a click the page where the user already is, is an indication of a careless, unreasoned design.