Tag Archive / web development
Finding a way to frame and hang this quote somewhere in my office space…
Stop drooling over your tools. Start thinking about what you’re building with them and how that’s affecting the world you’re helping create.
— Aral Balkan (@aral) May 10, 2014
Three months between posts. Sorry for the long delay. Been rebuilding…
Earlier in the year, I went to the IxDA Interaction 13 conference in Toronto, Canada. I have two more conferences for this year.
Next week, An Event Apart DC in Alexandria, VA (another serving…).
Then, in late October, CSS Dev Conference near Denver, Colorado.
As of this entry, finishing contruction/testing of the WordPress theme. Will be writing blog entries related to the whole history/process of Project Charles. Debuting on Monday, August 5.
August is going to be a busy month…
The role of a front-end developer is to build interfaces that give the user access to information with the least amount of interference.
— Ivan Wilson (@iwilsonjr) January 28, 2013
a method of building a visual model of an web application UI/front-end layer
During the past four months, I have been presenting previews of sketches and notes from my notebook via Flickr.
- Previews – Project Ottawa/Second Draft
- Previews – Project Ottawa/Second Draft (Modeling Example)
- Previews – Project Ottawa/First Draft
Project Ottawa [or the Ottawa model/diagrams] started in late February, prior to my trip to Ottawa for Jonathan Snook’s SMACSS Workshop. It was there that I did the first initial sketches post-workshop and a few weeks later, created the first draft.
After some review and criticism from a fellow co-worker, I decided to work on the second draft. This took more twice as much time as the first, with testing and constant revisions. However, at this point, I am writing the final pages and presenting the Second Draft as a microsite in early/mid July.
In short, the model is based on a) recent work on modularizing CSS (via Nicole Sullivan, Jonathan Snook and etc), b) analog to linear algebra, most specifically linear transforms, and c) my ideas on the UI layer, based on a concept called The Information Layer.
With these three items, I designed a visual “code” with symbols representing blocks of programming code and content. By examining mostly my own work, I developed the rules and basics to use the symbols to represent not the parts of the web application system, but also describing interactions withing the system.
The original purpose of this was archival, record keeping for myself. However, I began to realize that there was nothing out there that visually describes the work that FEDs [front-end developers] were doing. We have code and and can talk about CSS, HTML, etc. But, maybe for the first time, there was something that allowed the work to be visualized and be more tangible.
Currently, this is the second draft. Even though models are always being revised and changed, I kept the term “draft” because I wanted to present the working model in a state that was good enough for demonstrations. However, this draft appears, so far, to be close to being stable. Naturally, there is more work in the near future.
As I mentioned before, the final document will be presented as a microsite around early/mid July.
Before that, I created a single page preview, giving a brief overview of the model and its use in “mapping” a single page, AJAX driven site. This is based on the sketches/drawing from the last Flickr preview and the same example will be used as a case study in the final document/microsite.
A couple of months ago, I was looking at a promotional video touting some new technology. Something that was written solely for mobile. They went on about their processes, that by focusing not on the desktop, they were saving file size and increased performance, which is all and fine. Anything to life better, especially on those days when I want information without waiting for everything to compose itself during the morning rush hour. But at the end of this, I wanted to ask this question (which, in hindsight, I should have added to the comments):
Why should there be anything difference between the desktop and mobile?
Before answering, think about it real hard.
Don’t worry. I’ll wait…
The current paradigm of mobile is based on two things; the mobile phone and the tablet. But isn’t this the same sort of think we had before – the PC as the desktop. Didn’t we got over this? I got over this years ago, especially when my previous job required me to work with both Windows and Linux.
What I am thinking is that the current paradigm is just as short-sighted.
Let me put it this way? In a year or less, why not see a mobile device become the desktop?
Why not give the "desktop" have touch-enable events like its mobile cousins?
What I am imagining is the mobile/desktop schism not just disappearing. It simply gets redefined.
If my life is nearly almost located within the confines of my mobile phone, why not go all the way?
Our perception of the desktop is that of the monitor tethered to an external hard drive and et. al. What about a rapidly approaching near future where our version of the "desktop" is a mobile device tethered to cloud storage.
Just a thought?
Don’t wait too long.