Today marks the start of a concept that began in my mind around 10 years ago.
This is a concept that is, frankly, too big and furry for me to chew on my own.
And this idea just keeps bouncing back in my mind - forcing me to try again.

So from today I take another stab at it -with fresh insight, new technology, experience and more importantly, excellent people around me to bounce design ideas off of.

Enough of the rambling. What am I going on about..

Computers should work for us
We (humans) waste so much time trying to understand computers, when the technology is at an age where it really should be able to understand us.

Project ‘Swift’ embodies the concept of speaking to our machines in a more intuitive way with as little pointless complexity as possible. The ‘boring’ complexities should be in a dark corner and ‘just works’.

Application
Since this is such a huge and fuzzy task to achieve, I’m forced to focus on particular applications for it: a BI tool, a simulation/scheduling tool, a scripting tool.

In the end, I would envisage this becoming ‘built-in’ to your desktop/OS and become a natural way of controlling your computer, being able to generate quick scripts as well as enterprise level system solutions (A long and ambitious road, I know)
On the enterprise level, I also imagine that collaborative coding could become possible (and darn fun!)

It’s quite tough to describe what I’m imagining though (and for that reason, really important)

General Priorities
1. Logic modeling - Less code, more easy-to-follow logical representation
2. Flow & usage - The UI shouldn’t fight you, it should enable you. You should feel ‘zenlike’.
3. Dynamic scope - You should be seeing the relevant info at any point in time, and nothing more

Development specifics
Currently the specifics to solve the goals are:
- Visual solution modeling using multi-dimensional graphs representing the logic
- Flowing intuitive radial UI system, preferably with multi-touch support. Mouse usage in the meantime with key shortcuts for the keyboard jockeys.
- Object/Entity oriented, but default use is simplified. Advanced features easily available once you’re comfortable to use it.
- UI is highly context sensitive. Most likely desired options is considered and prioritized to avoid being overwhelmed.
- Zooming, drilling & generally flowing interaction between entity graphs. Drilling involves higher/lower levels of functionality

More specifics and less fuzzy stuff in my next post (hopefully)