Tag Info

Hot answers tagged

27

Update: In Mac OS X 10.10 Yosemite and later, it seems the zoom button has been replaced by the fullscreen button. The green widget no longer contains a plus sign, but two outward-pointing arrows, and places the window in fullscreen mode. To zoom a window, you now option-click this button. The green button isn't for maximizing. If you want to maximize, ...


22

The window expands to fit the content, and don't add additional whitespace like windows OS does. Now let’s look at Apple’s website in Safari. Notice the first image below is a very small window with both vertical and horizontal scrollbars. The second image shows what the window looks like after clicking the Zoom button. Again, it takes up all of the ...


14

Two thoughts that come immediately to mind is to include a slider that is always at 100%, and allow the user to adjust the size of different segments. Allow the user to add, or remove, segments as needed. Another option might be to do the same with your graph. A slider plus a pie chart is visually busy, so why not combine the two? Be careful of ...


8

Its because Apple explicitly mentions in its Human Interface Guidelines that all software providers should provide all functions available with a single click and they dont see any use case for providing a right click. That said it does support an option to have a secondary click as shown below which brings up the contextual menu Now coming to the reason ...


6

it's a status bar. it's not specific to osx, all browsers have one. it used to show the url of hovered links, status of requests, etc and then some add-ons/plugins started using it to show information. Recently it's been reduced to a something like a tooltip in most browsers (it only appears on mouse over links or when something is loading, etc).


5

Maintaining 100% will be impossible without adjusting other sectors any time the user changes something. That is likely to be confusing. Perhaps you could use visual feedback to show the unallocated amount or overflow. Instead of a pie chart, show a progress bar with a segment for each amount. If the total is less than 100% show the unallocated amount at ...


4

Apple has created the OS X Human Interface Guidelines, which describes the user interface, and other aspects, ought to behave on OS X. Moreso than Microsoft or other companies, Apple strongly encourages developers to follow these guidelines and I believe that OS X users have an underlying assumption, whether they realize it or not, that an app they use will ...


4

Some small issues about the current UI: The destination is before the source. The first dropdown has "---" pre-filled, but not the other one. The "Setup Enterprise Automatically" checkbox is not clear. You explain it right below but as a user, I would expect the whole setup to be done automatically. I would use such a phrase on a button, not a checkbox. ...


3

This is a status bar. In Cocoa programming you can create this by adding a custom view on the bottom of a window and using a text field to show information as required. Note that in OS X programming, the "Status Bar" (class NSStatusBar) refers to the the rightmost portion of the system-wide menu bar, with all the little icons, the clock, spotlight and so ...


3

Just so it's explicit, the full list of default point sizes for type in OS X is as follows: 9, 10, 11, 12, 13, 14, 18, 24, 36, 48, 64, 72, 96, 144, 288 There are two competing historical reasons why this set was probably chosen. Before System 7 (released in 1997), all fonts on the Mac were bitmap fonts, rather than TrueType outline fonts (chiefly because ...


3

Microsoft and Apple have slightly different UI guidelines, which I think you should adhere to. It may be important to note that the latest OS X Human Interface Guide hints a near-future shift towards touch supportive desktop interfaces. Which, if complied with, could mean a radical application redesign. The same is also already true for windows 8 ...


2

Having a simple UI does not need to mean a loss of functionality, it means a prioritization of functionality. I would suggest "focusing a fresh approach", as you said, and when you do so, start with the following: List all your desired functionality and features. Distinguish between the two. Functions are transparent to a user, while the features fit into ...


2

Hopefully the mock is comprehensible enough: download bmml source – Wireframes created with Balsamiq Mockups (the values below graph are obviously made up) The white dots (could be replaced with some more intuitive symbols) would be draggable and as in the result, the range's values would change. Optionally, clicking on a value would make it ...


2

Your application should meet the expectations of your users. If your users are Mac users, then you should follow their expectations for how Mac applications should behave. The interaction design of your existing Windows application isn't as important as the interaction design that users expect. One of the major strengths of the Mac platform is the ...


2

Dropdowns are good if there are a lot of items (it seems like it's not your case). Radio buttons are good choice if there are just a few of options (or any visual similar kind of controls). There is no need to show a control at all if only one singe item is available (like only one USB drive is plugged in: a majority of cases I believe) Try to avoid ...


2

The mice that come with Macs today have effectively more than one button, a press on one side is considered the primary button and the other side the secondary button. The primary button is associated with selecting and dragging and activating (with double click), the secondary button usually pops up a context dependent menu. Earlier Macs had only one ...


2

It makes no sense in theory, but can be highly justified in practice. The Apple bundle case One example of practical justification is provided by Apple: While the Contents directory might seem superfluous, it identifies the bundle as a modern-style bundle and separates it from document and legacy bundle types found in earlier versions of Mac OS. Now ...


2

Without looking through the internet for help it is a steep learning curve for some new users. A massive part of Apple's product is having the support to complement it, in this case the Genius Bar, and also telephone support. I first got a macbook around 6 years ago, and I also struggled to work out how to rename a folder. I achieved this learning by ...


1

It was wise to group all of the standard OS GUI window resize buttons, although the Miniplayer button in iTunes is still on the right-hand side, but neither the traffic light color scheme (which was kept from previous versions) nor the complete replacement seem very intuitive. Full Screen mode makes sense for some applications, others should have Best Fit ...


1

What you need is the ability to have over and under allocation so they don't have to micro manage every element, yet also prevent them from leaving before their total is 100%. Combining the pie graph with your list view and adding an indicator of "available percentage" at the bottom of your list will allow them to manage things either way. What I think is ...


1

You should create the application that your target users need. This means that you should understand why Mac users would want to use your application, what competing products exist on the platform, and how your product would fit into their current usage. Additionally, you should understand whether your target Mac users would also have experience with your ...


1

Mac users can deal with complex UI, like Adobe and Maya. Windows users appreciate streamlined interfaces as much as Mac users. When porting to Mac, it is essential that you have genuine Mac UI person on your team, who understands specifics. Some typical issues are: Macs have different common menu layout and keyboard scheme. Make sure your Preferences and ...



Only top voted, non community-wiki answers of a minimum length are eligible