Skip to main content

iOS 7 interface design looks familiar

Without much "hands-on" time with an iOS-supported device, it's difficult to tell for sure, but something looks very familiar about the design cues of Apple's new mobile system.

In spite of the noise Apple made around it's announcements a few weeks back, all the talk around the Web seems to be focused on the new "flatter" look of the interface design.  What seems to be coming out of this new look has been a move to look more like Android.

A flat look is not, by itself, revolutionary.  Everyone is doing it, but when Apple is taking more and more "heat" about no-longer innovating, following suit in the design department too is certainly not going to help cool things down.

For some examples of this similarity, take in the pages below, but bear in mind a couple of points.  One is that this example is of a dialog box in each of iOS 7 and Android 4.1 and to be honest, there's probably not much room for anything ground breaking can be done with them, design-wise.  But the button idea is exactly the same in each (rounded corners in iOS noted).  Second, it's true that one is white and the other black, but the Android Holo interface has support for both light and dark themes.


There's no criticism intended here, just an observation and a report on the findings.
Labels:

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more