Also, removing the file system tree would be a huge step backwards. Organizing hundreds or thousands of files between dozens to hundreds of projects is just not suited for a "everything in one searchable bag" for a few reasons: To find something with search, you have to already know what you're looking for - something that browsing a folder solves instantly (how can you know you see all relevant files with a search? Maybe there's an important file that didn't match your query?!) - and the common "solution" with tagging/labels are just single-level folders in disguise....
I'm glad Apple decided to not port OSX to the iPad, or replace OSX with an iPad-esque iOS. Most people I've talked to that experienced windows 8 would agree that when Microsoft did just that, it was a misstep.
Absolutely agree. I also fully believe natural text search is the future for computer interfaces. But what this article ignores is that you can easily have both. I use Spotlight to instantly full-text search over all of my files, applications, and their metadata to launch / open / access my data, but I also keep a standard directory structure instead of keeping all my files in one place. I've started thinking of the directory tree as a hierarchical tagging system, and when I'm trying to find a file for which I can't remember the right search terms it's incredibly useful. No need to throw out the baby with the bathwater; multiple views / interfaces to the same data is very useful.
I suspect Apple was thinking along the same terms when they introduced the "All My Files" shortcut in the Finder. But I'm sure they realized that the majority of their customers (who are barely able to use their computers; more or less computer illiterate) are just not ready to move beyond the "Desktop" / "Filing Cabinet" metaphor.
Actually, I've been thinking about this a lot recently, and I just started using the OS X universal Help menu feature [0] to take actions in complicated applications like Photoshop. Full-text search over all possible menu commands in any application? Yes, please. I really miss being able to do this when I'm in my Debian or Windows environments.
[0]: described here http://lifehacker.com/5592856/use-os-xs-application-help-men...
Tags are best when used to complement the hierarchical-folder-based system; as an extra layer of organization, not as a replacement.
Tags effectively let you keep a single file in multiple "folders", because the reason you're looking for a particular file is not always the same.
For example, my girlfriend is a concept artist and we're both fans of anime, so we trade a lot of reference and "reaction" images back and forth. Without tags, we'd be limited to keeping each file in a single folder, usually the name of the series OR a single character, but we're often looking for images depicting specific emotions, such as "Happy", "Shocked" and so on, and most images usually have multiple characters. With tags I can just save the image under the folder for a particular show, and just tag it with the characters' names and emotions. Keeps everything tidy for the OCD in me and makes searching for anything a snap as well. :)
That really struck me, because I'm of the latter type, and it makes me somewhat uncomfortable to have a search paradigm thrust upon me.
I'm also really missing the windows 95/98 start menu that would open sub menus instead of just being a view where stuff slides around.
Overall, what a disappointing set of ideas put forth by this article...
Actually Windows 8 can't be a misstep because it led to UI optimization for Windows 10. Windows 8 was just a drastic change for sure, but once you understood it's concepts it was really well suited for beginners and power users alike. The only misstep I can think of with Windows 8 is calling the Start Menu a Start Screen. That made it seem entirely different, when it wasn't.
Tablets and smartphones have a touch screen, computers most often don't. Software that doesn't take this into account will be a second-class citizen on the respective platform.
And while a flat filesystem with a powerful search function certainly has its uses, I wouldn't want to use it for everything. I'm far too anal when it comes to organizing my source code, for example.
The article touches on a concept called 'loops' for cases such as this.
I think there's room for innovation with filesystems. Personally I'm a fan of the 'database filesystem' ideas from BeOS/Haiku.
And I might be a bit pedantic, but filesystems are databases. Indexing and navigation methods sometimes differ, but a lot of people use advanced indexing in windows that not only checks extended attributes but also contents. etc.
How do you see that working well?
Microsoft tried to incorporate all the stuff like MP3 metadata into explorer way back when (XP? Vista? Can't recall)
OS X has supported "saved searches" which act like a live database-backed file manager ever since Spotlight was added. More recently they added quick tagging of files.
What are you imagining that would be more usable than these?
Well all the PC's in my home have touch screen and I surely miss it when I use a Mac at work.
I get hundreds of emails a day, work in an editor that is indexing ~11000 files, regularly have 50 tabs open in Chrome, etc. I find many apps that follow the sorts of aesthetics and principles shown in these mockups just do not scale to what I would consider normal professional use.
- A "people focused" email experience doesn't work very well with monitoring emails. I've had to turn off Gmail's smart inbox because me being CC'd into a person to person thread that I don't care much about is "high priority", but that Monit email saying CPU is at 99% on one of the webservers looks like every other Monit alert, and is a low priority update.
- I use Slack extensively at work, but email is still incredibly important.
- I may not need 50 tabs open, but after my 5 pinned tabs, a few reference/documentation tabs, the prod version of what I'm working on, the local version of what I'm working on, the PR page, and a few tabs of personal stuff, I'm easily reaching 20+, all it takes is one context switch to a different project and I've opened another 10. 50 isn't uncommon.
- A hierarchical file system is pretty important when working with Git repos. And I'm not a contractor, but if I were, separating client data is of paramount importance.
Apple will just keep improving iOS to be more powerful, more flexible and so on. The iPad Pro with iOS 9 is just a rough draft, it will be iOS 10 or 11 that'll show the hardware off, at least I hope. iOS 9 was probably the biggest jump in productivity for the iPads and hopefully, Apple keeps it going from now on, not neglecting it like it did prior to iOS 9.
IOS would have to evolve a lot and in many ways to take over desktop. Maybe it will. Android N seems to be moving there so maybe that's the future.
For developers I think the future is cloud based web dev setups anyway. I really like kicking off a large build or run on a remote server and not have it heat up my laptop. For different purposes, having a few beefed-up VPSs available and services like nitrous is more convenient. That said, developing in Emacs or vi in SSH term windows lacks some convenience, so it having deep integration of IDEs like IntelliJ with your own server build processes would be interesting (and even more interesting to also have great iOS and Android support).
EDIT: more on the topic of OSX: I much prefer the small continuous update process that OSX and Windows 10 seem to be taking. I use Ubunutu and I often think that I would prefer small continuous updates than 6 month drops - at least for laptop use.
It wrecked Pages, which was one of my favourite software tools prior. I use very little Apple software now.
...Ubuntu here I come.
There's absolutely no way you could build an app in a big "bucket 'o' files". Sure, you can put together a flyer for a softball game or (maybe) type up a simplistic report for school, but eventually these "loops" are going to become big, unusable buckets of content that isn't easily searchable (do we have good search on music contents yet? better hope the filename is good before it goes into the bucket!).
Perhaps the answer here is a "subloop". That's starting to look like we've come around to nested document folders again, isn't it?
Somewhat amusing: the screenshot of Sublime Text in the mockup is using folders.
Like the author, I worked on a distributed cloud FS, but hierarchy was a core goal. The abstracted reference system of HFS that split meta-data from the data resources is a huge boon to handling various common issues, from rights management to doing "fast" full-tree cloning over a distributed store and several other neat tricks like persistence. The biggest issue with distributed heirarchial file-systems is probably how to handle the full-tree cloning, in a way that isn't crippling, slow, or causes an enforced depth and file limits.
Analogies I'm thinking of include Smalltalk images, or how a compiled .app is a directory right now.
Why do I want Netflix and CNN apps that have been so easily (but nonetheless with effort) adapted to support the platform from their iOS counterparts? I expect I'll choose the website in Chrome every time.
Completely superfluous, of course, and they are probably going with macOS, but one can dream of a more sensible casing future.
edit: "macOS" is absolutely brilliant though. They should go for the throwback hipster vibe.
That sounds like it could work in theory, but I dunno if I'd actually want that as a power user. Mostly because there's more "normal" users out there, I feel like any alternative UI would be neglected. Seems like you'd be consigning yourself to being a second class citizen.
Maybe this works on Linux where there's less of a profit incentive because development on niche WM's and such is largely done by hobbyists, but I'm having a hard time imagining Apple spending a lot of resources on developing something large for a minority of users. Maybe if they opened it up a bit and had some sort of open plugin based build-your-own experience that could shift some of the effort off of them? I could see that working but it doesn't seem in line with Apple's philosophy.
Organizing files into projects is waved away by "just search through an amorphous blob of data". "Kind: PDF". Who finds files like that?
The user activity thread is nice, but it's clear Apple was already working in this direction with the links timeline in Safari, but all the social service TOS's forbid this kind of presentation and they're super-protective of their presentation to the point even Apple can't negotiate past it at this point.
Designer: design isn't just about looking sleek, it's primarily about meeting the use case as simply and robustly as possible. All these use cases are better on other devices.
1. Fix Finder. 2. Integrate the iDevice simulator into the OSX: all iOS apps can run on OSX. So let them. 3. Continue making kick-ass laptop/personal computers, with keyboards and screens and touchscreen, and make the difference between iOS and OSX go away, at the hardware layer.
Plan B:
1. Put Xcode on iOS. 2. Make an iOS Touchscreen Laptop (8-core ARM with 16gigs RAM, etc.) 3. Abandon OSX completely.
