HNHacker News
TopNewBestAskShowJobs

anonyfuss

159 karma · joined April 27, 2013

submissionscomments
anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
Which of the top apps look like https://www.joingrouper.com/assets/new_landing/OnboardingScr... ?
anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
> ... Google Maps etc.

I don't use the others, but I often get confused using Google Maps because I have no idea what all the new/unusual UI elements do.

Once I learn Google Maps' way of doing things, I don't want to have to learn a new way for every other app, too.

More to the point, I'd rather not have to learn how to use Google Maps' nonstandard UI to begin with.

> The rumor is that iOS 7 is going to change to a flatter appearance anyway, so in a few weeks this all might be moot.

That's a good point, because the way Apple rolls out incremental UI tweaks is by changing the standard components in backwards-compatible ways.

If you roll your own components, you have to work harder to keep up.

I would emphasize the word "incremental". If you examine the progression of Mac OS X across the past decade, there are significant changes, but they were done cleanly and incrementally and in a way that was immediate familiar to existing users.

I do not believe that we'll see iOS 7 pick up 'flat design' as defined here.

anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
If the approach propagates because community norms fail, then a bad UI (and another, and another) may result in the shared investment in common platform conventions being lost.
anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
> If it's not good less people will use it because users will not like the UI.

It's not quite that simple. If you want to use Netflix, you have to use their terrible webkit-based app. So we all do.

That doesn't mean that everyone would have a better user experience with apps sticking to common platform conventions.

anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
Apple's 1984 commercial was targeted at their users, not developers -- at least not in the way you're thinking.

The first Apple HIG was published in 1977 for the original Apple II. It was written by Bruce Tognazzini: http://en.wikipedia.org/wiki/Bruce_Tognazzini#Background

He and his partner, John David Eisenberg, wrote Apple Presents...Apple, the disk that taught new Apple II owners how to use the computer. This disk became a self-fulfilling prophesy: At the time of its authoring, there was no standard Apple II interface. Because new owners were all being taught Tog and David's interface, developers soon began writing to it, aided by Tog's Apple Human Interface Guidelines, and reinforced by AppleWorks, a suite of productivity applications for the Apple II into which Tog had also incorporated the same interface.

And thus interface standardization was born, out of the cumulative, compounding benefit of fulfilled user expectation.

As developers, it's our job to be the wizards behind the curtain. The users are the star of the show, not us, or our egos.

anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
What would you do if I published a broken password hashing scheme and encouraged others to use it?
anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
> This isn't some massive new UI paradigm ...

Flat UI isn't some massive new UI paradigm? I thought that's exactly what it is.

> ... it's effectively a theme!

One of the major components of the success and pleasantness of iOS -- and Mac OS X before it -- has been platform consistency.

Apple has made a study of this, and that's part of what users are buying when they buy Apple's products. Dismantling that consistency (rather than, say, building on it) is detrimental to your user's experience and the cumulative value of both the user's purchase and training, as well as other developer's investment in furthering the platform.

There certainly can be a fine line between building on the platform standards and dismantling them, but rewriting all UI components is very much on the side of "dismantling".

anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
Or, perhaps, the standing community can help enforce community and platform norms, as we're apt to do, by explaining what those norms are, and why.

And then, perhaps, we will preserve one of the things that has made iOS, and Mac OS X before it, such a pleasant platform to use: platform consistency.

Oh, the horror.

anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
Disregard this fellow's feedback, since he clearly has disregarded the platform users and the shared conventions of the platform community.

These elements don't maintain the look and feel of the components at all. They're roughly in the same place, most of the time, and that's about all you can say for them:

https://www.joingrouper.com/assets/new_landing/OnboardingScr...

> Sheesh, even Apple recognized that developers wanted to give their own look to controls by giving them Appearance hooks.

Yes, which you can use without breaking users' expectations, because they still look like they belong. They truly are re-penciling, not a rework of the UI to look like Windows Phone.

anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
The platform has defined conventions. There's a set of Human Interface Guidelines, and those guidelines prescribe what UI elements to use where.

There is also set of standard user expectations, and a general design culture that ties the platform together for its users.

On top of this is the massive investment that Apple has made in educating users of what to expect from the platform -- an investment that is further strengthened each time a user uses an app that follows the expected conventions.

Further, users buy their phones for this cohesive platform experience. If they wanted flat UI, they could buy a Windows Phone. They haven't.

So yes, forcing a completely non-standard UI on users, and promoting its use on the platform, is condescending and honestly hostile to the health and cohesion and shared value of the platform.

anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
Assuming the structure is preserved, all the visual language still has not been.
anonyfuss··on Show HN: FlatUIKit - Flat UI components for iOS
This total disregard for platform conventions does your users a disservice by making moot the effort they've spent learning how the platform operates and what to expect from UI elements and interactions.

On top of that, you have to reinvent all the native components you otherwise would get for free, and your app looks like an ugly odd duckling on the platform.

Why do this? It demonstrates an insane level of condension towards your users, the platform they've chosen, and the time they've spent learning it.

anonyfuss··on Firefox, Heal Thyself
I organize projects on multiple virtual desktops -- I usually have 3-5 personal software/electronic projects going at a time, and I switch between them throughout the week depending on what I feel like focusing on. Add to that 1-2 work work projects, and I'll have between 4-7 activate project desktops at any time.

I do most of my project research and documentation lookup in the browser, which means I might have anywhere from 10-30 tabs of pertinent information corresponding to each project on each virtual desktop, across multiple browser windows.

This is just convenient for me; I never have to swap in application/desktop state, because all my information, files, IDEs, etc are right there, exactly the way that I left them.

That comes out to 210 tabs at the absolute maximum; right now I seem to have around 100 Chrome tab process running. Fortunately, RAM is cheap these days.

anonyfuss··on Saurik releases Substrate for Android
No. No no no no no no.

There's nothing wrong with hacks. There's nothing wrong with runtime patching. If you know what you're doing, then you know why you shouldn't do it, and thus you're well equipped to do it anyway.

There IS something wrong with bundling up hacks and runtime patches into a simple user-friendly installer that leads users to believe that they will work and are safe. When the hacks fail (and they will), it happens in ways that leave users confused, frustrated, and blaming us -- the developers of the applications that your hacks crash.

Bug reports from people who use Mobile Substrate are a massive waste of time and user goodwill. They pollute our crash reporting system, they make users think our software is broken, and they result in bad reviews in the app store.

You've just made life more ugly for every ISV that supports Android -- and our users -- after doing the same to us on iOS for years.

anonyfuss··on Aaron Greenspan sues Facebook, Sequoia, Andreesen, YC, others
> The funny thing is it came to my house yesterday as a single cover sheet plus a CD-ROM full of files, and I literally don't have a way to read a CD-ROM anymore.

This doesn't seem very funny.

anonyfuss··on Creating a hacking environment for girls in Chicago
Someone donated enough for them to hit their goal (on the main project page):

https://www.piggybackr.com/girls_computing/chicago-girls-in-...

I'm sure they can put additional funds to good use, I'd encourage others to donate, too.

← PreviousPage 3 of 3