(Replying to PARENT post)

"The creators of Garageband for iPad didnโ€™t care about what their software could do. They cared about what people could do with their software."

Aren't they the same thing? Feature lists describe what your software can do, which shapes what people can do with your software.

That GarageBand for iPad is accessible to all might be more to do with the platform than the featureset.

๐Ÿ‘คmodernerd๐Ÿ•‘14y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

How to remove Red-eye in photoshop: http://graphicssoft.about.com/cs/photoshop/ht/apsredeye.htm

How to remove Red-eye in Picasa http://graphicssoft.about.com/od/picasa/ht/redeye.htm

Both pieces of software can remove redeye. For Picasa the instructions boil down to "Click the Fix Red-eye button" whereas Photoshop involves layers, Gaussian blur, saturation, eye droppers.

Which would you say is more accessible for someone maintaining a photo album? Photoshop has more features, but Picasa is more useful to me (in a certain context, obviously.)

๐Ÿ‘คparfe๐Ÿ•‘14y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

I don't think they are the same. We used to provide training for high-end medical devices. The manufacturers would often have a lot of features that looked good on a spec sheet but they were so complicated to use that no doctors ever actually used them.

Technically, they had the feature but the feature didn't help the doctors be better doctors. Features don't automatically translate to outcomes.

๐Ÿ‘คgdevore๐Ÿ•‘14y๐Ÿ”ผ0๐Ÿ—จ๏ธ0

(Replying to PARENT post)

Nouns versus verbs. A big list of what isn't meaningful if the presentation is such that people can't use it effectively. Most folks just want to get the job done or be able to play around without being pulled away from playmind by a nitpicky interface. Even if all the desired features are present, a poor design can make the product unusable or frustrating.
๐Ÿ‘คlocopati๐Ÿ•‘14y๐Ÿ”ผ0๐Ÿ—จ๏ธ0