OTGApps / rubymotion-inspect2014

Official App for the RubyMotion #Inspect 2014 conference in San Francisco - May 28-29, 2014
https://itunes.apple.com/us/app/rubymotion-inspect-2014/id863959924?mt=8
MIT License
34 stars 6 forks source link

Added inspect stamp to Default loader #32

Closed GantMan closed 10 years ago

GantMan commented 10 years ago

Proposed default loader for issue #30

markrickert commented 10 years ago

I'm ok with this. Not in love with it though. I'm more of a minimalist though :wink:

GantMan commented 10 years ago

wellllllll, I'm not gonna force it through if I'm wrong. Maybe we can get an outside opinion?

cc: @mattsgarrison @twerth @colinta @alloy

mattsgarrison commented 10 years ago

I just spent the last couple minutes flipping between branches, you could nearly blink and miss it. I don't feel very strongly about either version but I'd vote for adding the Inspect logo, as it's not shown anywhere else in-app.

mattsgarrison commented 10 years ago

What bothers me more is that it appears that the colors of the 3.5" version are subtly different than the 4" version.

alloy commented 10 years ago

Iirc, according to the HIG the default images should reflect the normal UI, but in a blank state. So it should not show a (big) UI element that’s never there under normal circumstances.

And especially considering that the image might only be shown for a short while (as is the case pointed out by @mattsgarrison), it makes the app seem less polished imo.

So I’d say no.

alloy commented 10 years ago

Supply a plain launch image that improves the user experience. In particular, the launch image isn’t an opportunity to provide:

  • An “app entry experience,” such as a splash screen
  • An About window
  • Branding elements, unless they are a static part of your app’s first screen

Because users are likely to switch among apps frequently, you should make every effort to cut launch time to a minimum, and you should design a launch image that downplays the experience rather than drawing attention to it.

Design a launch image that is identical to the first screen of the app, except for:

  • Text. The launch image is static, so any text you display in it won’t be localized.
  • UI elements that might change. If you include elements that might look different when the app finishes launching, users can experience an unpleasant flash between the launch image and the first app screen.

If you think that following these guidelines will result in a plain, boring launch image, you’re right. Remember, the launch image doesn’t provide you with an opportunity for artistic expression. It’s solely intended to enhance the user’s perception of your app as quick to launch and immediately ready for use. For example, Settings and Weather each supply a launch image that is little more than a static background image.

https://developer.apple.com/library/ios/documentation/userexperience/conceptual/mobilehig/LaunchImages.html

GantMan commented 10 years ago

@alloy agreed on the documentation... but it's obviously one of those rules no one listens to. Look to twitter, and google drive, and hangouts etc. They often show their brand in the middle while the app loads.

I'm fine flushing the style out, but not because of apple doc rules that are never enforced. I want your user experience opinion :)

alloy commented 10 years ago

With regards to UX, I agree with the guidelines, in this case :)

The image is gone too fast for me to be able to make it out and read the title. (Note, however, that I am on a 5s.)

GantMan commented 10 years ago

gonna kill this :) Survey says no go.

ty everyone for feedback :)