Also, if you think Microsoft's account management stuff is well put together, you... clearly haven't tried to manage a bunch of windows 8, XBox, skype and live accounts for an entire family over the past couple of years. It's a mess, and the only answer MS ever has for issues with an account is "make a new one".
In case you are wondering I switched my household, parents and several friends to apple products since 2002 because it was easier to provide help.
I sometimes wish there was a magic button I could push to merge everything into a unified single sign on for <insert company name here>'s products. It took a while but Google did it in a weird way that didn't make me very happy either.
The UI looks great though - if only office for mac proper could follow with the same quality, it would be great.
However, I can't figure out how to retrieve a .one file from the Mac Client to check for the format - anybody knows where it stores its file locally ?
[1] http://msdn.microsoft.com/en-us/library/dd924743(v=office.12...
Any sandboxed app has its data under ~/Library/Containers/<app>, then from that usually under the Data/Library folder, which is a kind of mirror of your user library folder, just holding that stuff the sandboxed app is allowed to see.
I am disappointed at the missing "Print" functionality as well as the broken "Email Page as PDF".
Now that a lot of the OneNote team seems to be around here I'd like to mention two issues with OneNote:
* Metro/modern/app-version doesn't support password protected notebooks. Client side encryption should be nice as well.
* Sane (>2005) tagging. Why oh why do you have to use the mouse (or several key combos + arrows in a row) to choose one of a list of predefined tags? (The checkbox feature is nice though.)For this reason alone, I'm still using a Windows VM simply for the "real" Outlook for work purposes.
If you drag one or more e-mail message out of Outlook for Mac, it creates .eml files. These are just RFC2822 MIME source with a file extension—almost any mail client out there can read them. If you drag an entire folder out, it creates a .mbox file. This is also a standard that many mail clients can read/import (Mail.app included).
Just wondering why the hell isn't this part of the export menu... great feature, undiscoverable as hell.
For better or worse, there were a lot of edges we didn't get a chance to smooth out by the ship date though I believe we made reasonably solid trade-off calls based on the team and deadlines we had. Updating the Export feature was one of those trade-offs (it's just not a super frequent user activity); that part of Outlook leveraged code from the much-despised Microsoft Entourage. The app was far from as full-featured as some users wanted (especially Win Outlook switchers) BUT did make enough progress to avoid the backlash of other "rewrites" out there (e.g. Apple Final Cut Pro X).
Little insider history: we did a lot to try and make sure data didn't get locked-in... we really wanted a place where, even if your app crashed, you could always get the data out of the app. During development, we even had builds where the entire underlying database was exposed as XML docs (one per item in your db). We couldn't get the perf we wanted out of that system. We ended-up with Outlook 2011's database which still bites folks from time to time but has a lot more "recoverability" than previous products such as Entourage (where it users often cited being locked-out of their database).
When we got to building Outlook, we decided to look forward—Cocoa and EWS only, building a strong base so that future releases could be far more capable. When I started on Entourage, the team was executing on a strategy to shove Exchange capability into a consumer-oriented app. It was shaky from the start, there were so many problems and customer complaints. I gradually learned as a PM that often a more impactful but riskier product strategy is to go big—instead of fixing 50 small issues a week at a time, fix 1 big issue that takes a year but renders the 50 irrelevant.
The only problem I know of with this approach, when coming from Outlook, are the Winmail.dat files that Outlook (or MS Exchange?) creates "to preserve text formatting".
Not Bill himself, but the OneNote engineering team are doing an AMA on Reddit on Wednesday at midday.
Nothing to link to yet but it's in the "upcoming" sidebar section http://www.reddit.com/r/iama
One Note will, however, appeal to people who prefer 'structuring' over 'tagging'. In fact, if you prefer tagging, look elsewhere. The tagging support here is abysmal. There are tags, but they are canned and the user can't add their own tags. So you have 'Definition' and 'Idea' (which thankfully is not "Idea!") and 'To do priority 2'. And only the ones that the people at MS thought you might think were important. Even more bizarre, they seem to be only visual labels. You don't appear to be able to search for items matching a given tag. Wtf. Am I using a computer or not?
I will say that they seem to have nailed all the account management, in particular two-factor auth, for the 'microsoft accounts'. But they did this largely by copying google's two-factor auth stuff. Which, to be honest, is what I would have done too since it's pretty good. Anyway, they don't appear to have screwed that up. That's a plus and not super-easy. Separate from One Note though.
The tagging fiasco and lack of export are both unconscionable though and embarrassing, imo. They are not an early entrant here; they need to do better than the competition, not notably worse. Plus this is an old product for them, just new to the mac. Bill, where are you? Surely this is easier than Malaria.