Safari on the iPhone offers users an option to enable private browsing. If you enable this setting, the browser will stop tracking your web history, your search history, as well as other user inputs such as usernames and passwords. Here’s how you enable the setting in iOS 6.0.1:
Today, I noticed that if I go to a user’s Twitter page while this setting is enabled for Safari mobile web, Twitter simply does not work. Here’s what the user sees in iOS Safari with private browsing enabled when the user goes to mobile.twitter.com/BillSimmons:
Essentially, the user sees a blank page with nothing in it. The expected result can be observed when the private browsing setting is disabled:
I really can’t think of a good reason for the Twitter mobile web experience to stop working correctly if the browser is in the private mode. Perhaps something having to do with cookies that Twitter is trying to manage on the user’s device and an error leading to nothing being shown. But either way, this is a predominantly read-only view and should be shown without issue to the user in either browser mode.
Noticed an interesting change from Safari 5 to Safari 6 in OS X. In the Safari 5 header, there are two text entry modules: one for the URL, and another for a search query.
In the upgrade to Safari 6, the two separate fields have been combined into one that serves as both the URL entry as well as the search module:
Some things that come to mind:
1. Looking back at the history of the internet over the last 20 years, there was a moment where Search got really big. What I mean by this is we reached a point where the majority of users who came to the internet initiated their session by searching for something. Very recently, say in the last 3 years, with the boom of mobile apps, there has been a shift away from search as the starting post and more toward apps as the starting post for the user. What I found interesting is that this browser change pushes the user just slightly back toward the direction of search as a starting point.
2. Apple vs. Google. It’s an open secret that Steve Jobs was not particularly fond of Google toward the tail end of his time at Apple. While initially Apple and Google had some partnerships i.e. Google Maps and YouTube being two of the very first native apps on the iPhone, the relationship between the two companies went sour with the heavy investment of Google into Android. Just recently Apple has received a lot of negative attention by creating their own version of Maps for iOS instead of using the already beloved Google Maps app. So in this angle, it is very strange to see Safari, an Apple product, make it much easier for the user to use Google.
3. Web vs. Mobile. While this change has been incorporated into the web version of Safari, the iOS version of Safari remains the same with two separate fields. This is interesting for two reasons: (1) Apple has created an inconsistent user experience across different platforms OS X vs. iOS and (2) It is strange to see two separate fields in the UX for the platform with extremely limited screen real estate. If anything, one could make the case that there’s more justification in the web flow to have two separate entry fields due to an incredibly wider screen than a mobile view which has a much smaller screen width.
Expose is a feature in Apple OS X that allows you to see all of your open windows spread out nicely in front of you. They look as though they are on your desktop, and then you can click which window you want to take the focus back to. Here is an example:
While viewing a PDF document in Safari, I noticed an extra window in Expose that did not belong:
The title of the window is AdobePDFViewerNPAPI (Safari Internet plug-in). The correct user experience would be to not show this extra window when a user is viewing a PDF document in Safari.