I’ve heard Ben Thompson pop up on The Talk Show every now and then, but last summer I was introduced to his podcast, Exponent. In their 100th episode, Ben and co-host James Allworth give detail the world since the introduction of the iPhone ten years ago. This is possibly the most quintessential episode of Exponent. If you have never listened to the podcast, this is a great place to start.
It’s not related to a bad memory or to aging, but rather to how the brain categorizes names. It’s like having special folders for family names and friends names stored in the brain. When people used the wrong name, overwhelmingly the name that was used was in the same category, Deffler says. It was in the same folder.
I have been buying media and software from Apple for a long time. Pretty much since the iTunes Music Store opened. Until yesterday, I have never so utterly regretted a purchase that I wanted a refund. Apple does not make it obvious how to accomplish this task, so much so I got a feeling that it couldn’t be done. I searched the Apple Support documents the best I could to no avail. Through a series web search landed on instructions start this process in iTunes by going to the Account page and viewing recent purchases.
Turns out there is an easier way.
Apple has a website built for viewing purchases and reporting issues with those purchases. The title of the site is Report A Problem, and at first I didn’t get why. I saw the full purchase history of my account from the iTunes Store, App Store, and even the Mac App Store. Then it dawned on me, it was everything in the last 90 days. The timeframe to report a problem.
What is nice is the purchase history can be broken down by receipts1 and product type as well as search. From what I can tell though, it takes up to 24 hours before a purchase will show up on the site. I was looking into a refund about 14 hours after purchasing.
Once the purchases, a Mac app and companion iOS app, showed up on the site I pressed the “Report A Problem” button. The area expanded to reveal a dropdown list and a text area to describe the problem. I selected “Didn’t mean to purchase this item” and for that the description was required. I left the Apple employees a lamenting response, hit submit, and was told to expect a full refund in five to seven business days. Easy enough.
The receipt bit is quite nice for those business reimbursement requests. ↩
Purchased templates get a bad wrap. Up until early this summer I was on the bandwagon, deriding the use of templates. But, then my colleagues and I had an instance where it made since on a project. My mind has shifted to understand why and how agencies can utilize prefab web templates to meet the needs of their clients. However, there are things to keep in mind when choosing this approach. Hopefully my article on the Sparkbox Foundry we be a useful guide for those weighing such a decision.
I joined several of my Sparkbox teammates this month a helped write a joint article for The Shift on the topic of Progressive Enhancement. I love the topic and I dive into what I love about CSS, the cascade makes progressive enhancement a natural aspect of the development process. The tl;dr on utilizing the cascade for progressive enhancement is to put styles for older browsers near the top of the selector block with newer properties toward the bottom. This works especially well for Flexbox properties, which I get go into detail in the article, so check it out!
Be sure to keep up with what others are writing for The Shift, with my list of Shift articles.
Last week I attend the CodePen Show & Tell at ConvergeSE. While there, I demoed Container Queries using a collection of demos I posted on CodePen. If you’re not familiar with Container Queries (a.k.a. Element Queries) I highly recommend checking out my talk on the subject from CSS Dev Conf last October, or checkout this list of resources.
Container Queries are still in an early concept state. More work needs done to make this a browser standard, but things still seem optimistic. There is need for more and more use cases though, and polyfills are a great start. Consider taking one of the polyfills from the collection for a spin. Hit me up on Twitter if you have a new demo to add to the collection.
Who Browsers Are For
The most pivitol tool a web developer uses day in and day out is a browser. They are what we develop for. Browsers can equally enstill excitement and dread throughout a project. As a web developer, it can be hard to maintain perspective of the purpose of browser—to meet the needs of the typical user.
Browsers are justsoftware and there are bound to be bugs and issues. Thankfully most browser makers have instituted short release timeframes to take care of minor bugs quickly. But even so, the browser makers’ priority is a feature rich experience for the user. These are features that aren’t associated to any standards, but instead provide the user with preferencial features. One of the reasons I prefer to use Safari has my main browser is the built-in feed reader and tabs syncing. Other browsers offer these features as well, but I like how Safari does it.
Browsers aren’t primarily made for developers, but they are a vital community to a browsers survival. At that web developers are completely reliant on the existance of state of browsers to accomplish their job. We need to maintain constant dialogue between web developers and browser makers.
Here is where you can log a bug for each major browser maker:
Follow The Browsers
Additionally consider following the Twitter accounts, blogs, and mailing lists of all the browsers to be aware of what they are up to. WebKit has a great blog, Chromium has a very active community forum, and Opera is quite intent on tweeting all kinds of things.
Make The Web Better Through Engagement
Take the time to document and report a bug, and make the web better.
I wrote a tutorial covering Element Queries for Net Magazine that appeared in last month’s issue. The web version of the tutorial is now available on their website. If you haven’t looked into element queries, it isn’t too bad of a place to start. In the article I give an overview of what element queries are, some simple use cases, and an explanation of using a polyfill.
The online version leaves out some aside content from the print edition, so below you can find some resources to further explore the wonders of element queries.
Articles and Websites
RICG is helping push element queries forward as a web standard.
By Tyson Matanich
By Scott Jehl
By Ian Storm Taylor
By Tab Atkins, Jr
By Daniel Buchner
By Tommy Hodgins
Today, Sparkbox launched a community writing project called The Shift. Each month a new topic is selected and the whole web industry is then invited to write on that topic. Whether it be posted on a company blog, as a Facebook post, or a Medium article, the hope is to spur a large conversation with diverse thoughts and responses.
Here’s how it works:
- a topic is announced on the first Monday of each month
- if you’re able to contribute, you announce publicly that you’re participating in this shift using “#startYourShift” hashtag -everyone is invited to research, consider, and publish about that topic on the last Friday of the month at noon Eastern
- all contributors share a link to their piece using “#startYourShift” hashtag on Twitter and any other platforms where they please
- we all get to be part of an industry-wide conversation on a specific topic
The inaugural topic is “How to Make the Web Better.” You can sign up to be notified about The Shift topic for the month, and get reminders as the deadline approaches for each topic. I plan on participating as much as I can on this site, I hope you will as well. Be sure to follow The Shift’s Twitter and checkout The Foundry to see what a Sparkboxer might have to say.