Filed under

usability

 

Snippet #1: Stylebot & Google Reader & More

Update I've also added one for the ReadItLater webapp. Both now feature css3 finishes and webkit scrollbars, which I think should be everywhere. Customizable embedded browser chrome (buttons, fields, scrollbars) is such a necessity these days.

Update All my styles are here: http://stylebot.me/users/hlfcoding

Update I've updated the Reader snippet to be even more ridiculously minimal. I've also added the snippets for some other sites. Note the gist contains versioning and are bookmarkable if you're on github.

http://stylebot.me/ is an awesome Chrome extension, doing what userChrome.css does in Firefox, though perhaps with more style. Here's something to help Google Reader power users *

(download)

* Use www.google.com/reader/view/ instead of the autodetected www.google.com


 

Filed under  //   development   open-source   stylesheet   usability   web   web browser  

Essay #3: Two Years of 2.0

blog post header: a garbage piles of bookmarks

I started seriously following web trends a few months before 2008. Now 2+ years later, I’ve deleted 500 bookmarks from my Delicious, almost a couple hundred+ tagged items from my main Reader account, and another couple hundred labeled as TODO from my browser bookmarks, stored by XMarks. Now, hours later, I still have another couple hundred items in my ReadItLater list, although somewhat sanely manageable and accessible. And I’m fanning the flame by writing a long review, hoping some upstart doing websites out there will find use in it.

Overall, I feel like all web news, lessons, and exhibitions was useful. I learned lots stuff good. But I spent much time and still missed some golden opportunities. On several occasions mostly in Delicious, I had duplicated entries perhaps only months apart. A number of the items I had as TODO were horrible write-ups on WordPress and jQuery “tricks” that were (in terms of screen estate) 20% awful UI, 40% yes-men comments, 30% ads, and 10% content. Only now do I realize how shallow those authors’ knowledge were, as I eventually outgrew the usefulness of my gathered resources. So yes, I should have organized better (more on that), but there is a definitely content quality issue with sites out there. Oh, and I’m also pissed FFFFound has no RSS feed.

Seems like posters of late don’t take the time to write and grow content but instead just put up link bait to worsen the quality of RSS feeds. Delicious Popular, back in 2007, did not look as it does today. Back then, since the web was less spammed up by WordPress strip malls, the content gathered by (what I’m assuming is and has been) an automatically ranked feed of popular pages on Delicious based on times bookmarked. As a result, the content was quite good, and I learned a lot about mashups, and startups, and CSS standards, and even design patterns and separation of concerns. Back then, there were no Noupe, Cats Who Code, etc., and point is, now my attention has shifted to Hacker News and a selected group of consistently good bloggers writers. Still, little by little the WordPress spammers are creeping in. I really don’t know how they do it, and I don’t think HN is very automated…

Read the rest of this post »

Filed under  //   algorithms   software   usability   web   writing  

Essay #2: A Case Against Closed Source

blogpost header: the dichotomy in goodness of apple's user friendliness and developer friendliness

The greatest thing about Google Chrome? I can download any extension, and if I dislike the UI the developer hastily slapped on there, I can change it myself in a few minutes. I can store changes however I want, back them up in case future extension updates overwrite them, maybe even send the guy my changes. The web is built on this dying code of ethics, one I will one day sorely miss. The web is shrinking and consolidating. Like the industrial revolution, there will be much turmoil, chaos, and injustice ahead. Unlike the industrial revolution, there is no guaranteed improvement in living standards. Maybe the leash around our necks and blindfolds around our eyes will tighten. But we will accept, even unwittingly, because there is no point of reference. There will be more monopolies than innovators. More fences than doors.

What building a walled garden does is it drives other people, whether through annoyance or motivation, to building their own walled gardens. The result is the new century's arms race. The stakes are users and their information. The end result is less functionality and freedom for the end user, who has to make difficult decisions and commit to certain technologies and platforms out of paranoia about identity security. But more importantly,

Why should anyone trust software, hardware, or services that refuses them access rights?

The web is also built on standards. Take aways standards and there's only chaos, inefficiency, and room for mishaps much worse than the typographic eyesore. By creating a new whole new 'ecosystem' of distributed applications outside of the internet and its protocols and technologies, there comes a great burden of re-inventing the wheel. Apple just declared war on the Internet. The walled garden versus the open prairie. Even if what Apple is selling works and looks better (at least on the front-end), it is poison. There is nothing worse than playing a game and betting your life on other people's rules. In the simplest of terms, it's a dictatorship versus a democracy. And while giants like Google can potentially dictate, they are more benevolent and aware of the community's needs.

Apple's war on the Internet is not a complete win. Much has yet to be done about Flash, about being able to search through an app collection wider than 3-4 iPhones. I would suggest the company rethink its goals, and also bear in mind: Why do I need an app that only a fraction of developers know how to build (thereby more expensive), only a fraction of people will get to use (thereby less profitable), and with a potential chance of being rejected by a third party; when I can build an app using open, common technologies like HTML, CSS, JavaScript, Java, Python, etc. Time spent focusing on shiny buttons is time lost on accommodating developers is chances of building real and useful apps wasted. Don't get me started on the idea of interactive ads. Most apps are already ads in and of themselves. Unobtrusive is the best cure for a necessary evil. Google already figured that out. Time to stop reinventing the wheel.

Back in college, if I had to get my old hellolittlefriend.com website approved by Google or Yahoo or Apple prior to launch, it would have never seen the light of day, and I'd be a few months less of a front-end web engineer. I might have never even gotten the needed break. The site was a UX what-not-to-do: CSS was wonky, the jQuery was horribly inefficient, and the Portfolio page had 50+ full-sized images. But no users were harmed in its making, and I learned from my mistakes. Coupling its review process with its hands-off-my-shiny-shell policy, Apple is doing such a disservice to education, I would suggest Mr. Jobs, in light of this hypocrisy, to retract his speech at the 2005 Stanford commencement. It turns out, never settling and thinking different are not always good.

 

Filed under  //   Apple   Google   development   usability   web   writing  

Essay: Navigating The New Housing Boom

blogpost header: a city of markup, a house in focus with #fff hex on its roof

Websites are like houses. The creator of Django confirms this idea I've had in my head for a while. While I lack his experience working with the internet, and I have not worked in construction or studied architecture, I see the similarities in the processes. I also believe these similarities will can help us correctly defined the future of websites.

Definitions

Most websites are, or should be, functional, so they're rarely foremost works of visual spectacle. I am excluding the genre of the Flash-based brochure sites, as they are closer to commercialized movies. I am referring to sites that foremost deal with data: its storage, distribution, presentation, aggregation, and management. Since the internet is about interacting with information, it doesn't do much good if the information is static, like in a brochure site. Therefore I'm referring to sites where the data is very dynamic. Of course, it doesn't matter what the site does; sites do a lot of things, from tracking your life to being a game.

If making websites was about visual spectacle, it would be more like making a painting or a movie, all about the visual feel with little concern about supporting functional, non-linear interactivity. Rather, making websites is different and harder in two ways. First, websites, like other software that support user-interaction are non-linear. This changes a lot of the underlying creative thought process. Instead of just imagining the natural, cumulative, visual progression of strokes on the canvas or frames in the clip, you have to think of use cases, the variety of paths that branch and fork depending on what the user is looking for. The user is given too much interactive power for linearity to work.

And that's how, for a while now, I've realized like many, many others, the website of our time is actually software.

Analogies

And making software is like making houses. Both tasks take a very long time. There are numerous stages, and I'm sure, variations of processes for projects of various scale. There are many components and with them, are constraints. And these standards must be met, or the result is unusable. Just like poisonous Chinese drywall doesn't meet standards, make people sick, and devalue the houses they're in; a website where there are ads anchored to malware or flash banners that interfere with the layout and content upon mouse-over will drive away readers and actually lower revenue, thanks to ad-block features on browsers and userscripts. Or something as careless as forgetting user-friendly color contrast.

Read the rest of this post »

Filed under  //   WordPress   design   development   frameworks   usability   web   writing  

Visual refinements

This Posterous thing is pretty neat. Although the interface is a bit clunky, with the new theme feature, I'm really sold on this as a decent, low-overhead blogging platform. I'll admit the default html/css doesn't exactly follow best practices at parts, but it sure beats what I've seen in some themes in other blog platforms; ahem WP. 

Filed under  //   Posterous   WordPress   blogging   design   usability   web