3 ms·
Sure, that is what I meant. My guess is that this app is giving us an early vision of what apps will look like in the upcoming full-screen mode. When that mode
by mechanical_fish 16y ago
Sure, that is what I meant. My guess is that this app is giving us an early vision of what apps will look like in the upcoming full-screen mode. When that mode comes out, not long from now, the App Store will continue to look exactly as it does now.
Why design the window twice inside of a year when designing it once will do?
Of course Apple won't take away OS support for draggable windows. That would be silly. What will happen, though, if the new full-screen mode takes off, is that app developers will redesign their windows to be more suitable for full-screen. And that may well involve smaller or nonexistent title bars.
- sudont 16y agoThat's already happened to some extent. Xcode and Final Cut both run in multi-window yet effectively fullscreen mode, but act as IDEs for their respective workflows. In fact, this IDE mentality could be the new big divisive topic in the Mac world: Coda vs Textmate and Safari and CSSEdit and Versions and... Really, it's the same war as Vim vs Emacs (somewhat), just with GUIs. Does the application need to be full-screen and kitchen sink, or multi-window and able to integrate with others? I do agree, this could be a nuclear, apocalyptic scenario. But while photo, video and code workflows can be condensed nicely into one app, traditional mac workflows have been multi-window, multi-app in that most common tasks aren't IDE-oriented, and constructed from many different apps running on the Mac platform. But, to counter your point about app laziness: most mac developers came to the platform to make really good apps. If it was about just throwing something easy out there, they'd have run to Windows or enterprise apps already.