Showing posts with label Microsoft Office. Show all posts
Showing posts with label Microsoft Office. Show all posts

Monday, August 20, 2007

Numbers rocks: how I forgot about the review and ended up doing my budget

Apple has made a trial version of the iWork suite available as a free download. Pretty smart move: the suite is relatively small (it fits on a CD), so this is a great way to get people test drive the latest version of this emerging little office suite. (Let me get back to the "office suite" part later.) You can buy an activation code online to unlock the trial version, so basically, Apple is distributing iWork '08 as shareware. Cool.

I've put Keynote and Pages through their paces, and they're OK. But what I've been most interested in was Numbers. Why? Here's a list why:

  1. It's new. Duh.
  2. It's a spreadsheet app, and those are relatively rare. Word processors are a dime a dozen.
  3. I wanted to see if Numbers is competitive with Excel.
  4. I work with data a lot (Excel, FileMaker, and so on), and wanted to see if this new tool is of any use for me.

As anecdotal as it gets, but still, wow...


So I fired up Numbers, and started off by using one of its built-in templates. I noticed one that was called "Budget," [edit: originally I wrote "Home Budget," not sure how I'd got that wrong] and thought, what the hell, let me try that one.

I've been putting off drafting an annual personal budget for quite some time now. I was looking for the right tool for the job. Now, it's important to know that I'm a tool freak. (Also a Tool freak, but that's probably beside the point.) That is, I can obsess about the right tool for the job a lot more than about the job itself. It's almost a policy. Yep, I know this can be a flaw. But not always.

Anyway. So far, I've tried creating FileMaker Pro databases, using and extending Excel templates, and I've always given up after a certain point. Building a FileMaker database is almost like writing an application: you need to do a lot of work before you can start using it. About Excel, I just didn't know where to start. The built-in templates weren't much use, and as for rolling my own: the task seemed a little too intimidating. Before getting on with the already daunting task of drafting a budget, I would need to decide on how many worksheets to use, what kind of tables to design, and how to interconnect them, etc. I'm not bad with Excel, but whenever I embarked on this budget project, I must admit that I always ended up giving up.

So, last week, I fired up Numbers, and opened its Budget template. It was pretty straightforward, I just about immediately figured out how it worked. And to my utter surprise, it was almost exactly what I needed. I made some small adjustments, and started putting in my numbers. Then I made some more adjustments to the template, consulting the help file two or three times.

After about five hours, I was still frantically, furiously working on my budget. I was sweating, but what I was fighting was my numbers, not Numbers. I didn't even notice the app was there.

And that's just about the best thing you can say about an application. It gets out of the way, and lets you do your thing. Oh, and the template is very nice, too. Maybe that's where Excel lost me on this one, and Numbers won me.


These are my first main observations about Numbers

Numbers doesn't have one workbook with several infinitely large worksheets. It has pages with tables, which are the size you want them to be. This doesn't only make your numbers nicer to present, but also makes it easier to work with them: you can see all the tables at the same time, you don't need to switch between worksheets.

If you mouse near the border of a table, some controls pop up. You can insert, delete, or drag and drop columns and rows, you can sort and rename columns, and so on. These operations are extremely intuitive, though really mouse-heavy: there are no keyboard shortcuts for most of these. Working in Numbers feels a bit more like working in InDesign, and less like in Excel, where you can let go of the mouse for quite some time if you want. To me, this is a clear shortcoming, but a tolerable one.

Numbers is very good with defaults: it knows that most users will want their tables to have headers; and that when you sort, you'll usually want to sort the entire table. (This is a pet Excel peeve of mine: using auto-filters, you can never be sure if your entire table is being sorted. Some pesky little thing can prevent some columns from being sorted, and you'll end up with useless data.)

While sorting is dead simple, there are no auto-filters in Numbers. Filtering is dialog-based, and clearly more cumbersome than in the Microsoft suite. Also, the only way to tell if your data is filtered is by noticing missing row numbers. Excel has other visual clues, and they are important. Probably Apple's research shows that people don't really use filters that much. It's a pity, because I do.

Tables can have headers by default (there are several table templates you can choose from, but you can fully modify a table after creation), and they can also have titles (captions). These are great time savers as you add and arrange new tables to your work area (called a Canvas).

Numbers makes sure your spreadsheets are neatly organized and beautiful. Just like a great schoolteacher, it will instill a sense of work ethic in you, inviting you to keep your work clean and well-organized. (Don't use Numbers for committing tax fraud or plotting evil schemes. You will break down with guilt and give up.)

One annoying bit: as you move or resize a table that has another table on its right side, Numbers will always move that table too, keeping the distance constant between the two, even if that's not what you want. (Thanks to the reader who pointed out that this behavior can be turned off in Preferences.) And believe me: you will care about how your tables look. Numbers will make you.

Cross-references between tables and cells are quite like in Excel, except that they use column and table names, not numbers. Luckily, these names update dynamically.

There's a generous helping of functions, and for obvious reasons, they have the same syntax as in Excel. Not nearly all of Excel's functions are present, though. Worse, I've been relying heavily on Excel's extensive help system when constructing a function: as you type, it displays the syntax for you, and mousing over each part will show you additional details. It's very easy to get specific help for each function. Not so in Numbers: you're pretty much on your own, and help is awkward. Functions are probably also considered an advanced feature that relatively few users would be interested in. Hopefully, Apple will beef up this part of Numbers for the next version.

There is one very useful feature, though, that immediately made me a fan (that is, if one can get fanatic about spreadsheets). Select a few cells in Excel, and the app will display the sum of all the numbers in them. Numbers takes this concept a step further: not only does it display their sum, count, average, minimum and maximum, but also lets you drag these to your table, as a really quick and easy way to create a summary field. Well done, that one!


Bloatware vs. clutterware

So Lasso is here, and it's sexy indeed. But does it take on Excel? Well, yes, and no. Excel has macros (though you'll have to kiss them good-bye soon, as they will be absent from the next Mac version.) It also has tons and tons and tons of advanced features that Apple did not include in Numbers.

Now, there will certainly be people who dismiss all these tons of Excel features as "bloatware," but I will certainly not go down that road. I'm with Joel Spolsky here: he believes that the size (and the complexity and the feature count) of applications increases as do our needs. He also gives us his spin the 20/80 rule, i.e. that while it may be that 80% of users use only 20% of the features, it's not the same 20% for everyone.

I do believe that software can be too complicated and intimidating (and Microsoft Office is certainly like that). However, that doesn't have much to do with the number of features, but rather with their presentation. I would rather call it clutterware than bloatware. Features are necessary, but throwing them all at the user in a big scary mess is wrong.

For a version 1.0 release like Numbers, Apple did have to narrow its focus on the most commonly-used features. However, here's hoping that the scope of Numbers will grow in time. And knowing Apple, I'm fairly confident that Numbers will never become clutterware. Bloatware maybe -- but, as Joel says, that's actually a good thing.

Is iWork an office suite then? It would probably be an inaccurate moniker, and one that Apple seems to want to avoid (never calling it an office suite, going with "productivity suite" instead). This has to be at least partly due to a marketing effort that carefully tries to avoid the appearance of competing directly with Microsoft. But marketing materials, as well as iWork templates, also clearly indicate a focus on the home, small business, and educational markets, Apple's traditional strongholds. Besides, large corporations would need collaboration features clearly missing from iWork.

I wonder whether Apple will, over time, address the corporate market more aggressively. We can say that, with iWork '08, it's on the doorstep, but not yet knocking.

Read More...

Thursday, December 14, 2006

Vista's 157 thousand new PR jobs

A 14-page IDC report (download PDF here), commissioned by Microsoft, says that Vista will create "157,000 new jobs."

Mac fans could (and do) take cheap shots at this number. "Yeah, right. Vista will suck so bad that you'll need 157 thousand people to answer tech support calls."

But these shots would miss the point. They would imply that someone seriously investigated how exactly Vista would effect the IT job and spendings market. Instead, here's what the study does.

  1. It forecasts that IT spendings, thus also the IT job market, will grow in 2007 in the United States.
  2. It then predicts that the ratio of "Vista-related" spending* (thus also jobs) will grow.
  3. As a result, 157 thousand out of the 400 thousand new jobs will be "Vista jobs."
  4. Then it concludes that all these jobs would be single-handedly created by Vista.
Never mind that Vista will be bundled with just about every new PC sold, so Windows market share will continue to be determined mostly by license agreements with PC vendors. Therefore, any overall growth in computer hardware sales will likely result in a growth of Vista's perceived job market share, especially since IDC classifies anything that "runs on or supports Vista" as a "Vista job."

If you buy a Dell, erase Vista from it, and install Linux, IDC says you'll still contribute to Vista spending. If a company replaces all of its five-year-old PCs with new ones, it will contribute to IDC's idea of Vista spending. If you're a software vendor, and your software happens to be compatible with Vista, you're contributing to Vista spending, and if you increase your sales, even more so, according to IDC.**

But it gets better. According to the report, "For every dollar of Microsoft Windows Vista revenue in the U.S., IDC expects $18.00 to be generated in revenues by other companies in the Microsoft ecosystem. " A graph shows that these 18 dollars are made up of $9.75 in hardware sales, $4.60 in software sales, and $3.65 in services.

Here's the deal. You buy a PC, it will have Vista installed, and you'll pay a hidden charge for it. If you're IDC, you'll interpret it as wow, a one-dollar income for Microsoft has just created a ten-dollar hardware sale. But then in IDC's world, gas spendings probably lead to car purchases, just as hangovers lead to parties.

But there's another approach. How about, "for every ten dollars of hardware sales, Microsoft receives a one-dollar tax"?

Because, you know, I'm sure all that hardware would run something, even if Vista, or Heaven forbid, Microsoft weren't around at all.

Well, IDC's gig as Microsoft's court poet must have blurred its vision:
While it is easy to think of Microsoft as simply the world's largest software company, it is more than that. It is an economic force that has a direct, positive impact on the countries in which it operates.
Full disclosure: this blog has never been sponsored by Microsoft.

*IDC must have meant to say Windows market share here, as most versions of Vista haven't even shipped yet, so it would be pretty bad for Microsoft if Vista's current, virtually non-existant market share grew one percentage point between now and a year from now.

**Someone should do the same math with Tiger (as well as Leopard). Mac OS X market share has increased lately, and I'm sure all those extra users would never have bought any kind of computer had Tiger not been released.

Read More...

Friday, October 13, 2006

Will Apple take on Excel, or settle for sexiest spreadsheet?

As PC Magazine reports, Apple is rumored to include a brand-new, full-blown spreadsheet application in the next release of its iWork suite. If the past is any indication, iWork's next version will be called iWork '07, and should be released next January.

According to PC Mag's article (written by Think Secret staff), the new component, codenamed Lasso, will try to compete with Excel without being too competitive, just like Pages fails to pose direct competition to Word.

That approach, which seemingly runs counter to Apple's recent Mac-PC advertising campaign, might stem from the company's respect for Microsoft's Macintosh Business Unit, whose continued commitment to bring Microsoft Office to the platform has helped make Macs more competitive in some environments.

Can't argue with that. Apple can't afford to lose Microsoft Office for the Mac, whatever a horrible beast that suite currently is on any platform. With Mac versions of Microsoft applications dropping like flies (Internet Explorer, Windows Media Player), Apple needs to be careful in posing competition to Microsoft's titles... At least, for now.

Perhaps one day, when Apple's top secret "Office Killer" inside iWork version (such a thing must exist, right?) is mature enough to be released and promoted as a capable replacement for Microsoft Office, Apple will launch an all-out attack against the Redmond productivity suite, even risking Microsoft's pulling out of the Mac market altogether. But until then, Apple needs to be really careful not to outdo Microsoft too much here. Must be a bitch of a feeling.

I for one wonder when we, Mac users (or actually the users of any computing platform) are getting a decent word processor that will, for example, get structured documents right.

Whenever I've attempted to use several levels of headlines in Microsoft Word, its unpredictable, counterintuitive, and sometimes downright buggy behavior has driven me nuts. I would usually quit trying and continue in Pages instead, even though Apple's word processor has, to my disappointment, turned out to be much more of a presentation tool than anything else, lacking some basic word processing functionality.

That, however, might change somewhat according to PC Mag. Even though Apple's walking on a thin line between complementing and competing with Microsoft Office, the upcoming Pages 3 is rumored to include a dedicated word processing mode:
The next upgrade to Apple's desktop publishing software, Pages 3, is set to receive a number of improvements poised to make the application behave more like a normal word processor. At present, Pages features a virtually identical interface for both standard document creation and more advanced publishing, but Version 3 will divide these two capabilities into separate Word Processing and Layout modes.
So Pages will move a bit closer to Word (or rather, let's hope it'll move closer to what Word should be), while Lasso will get Apple's foot in the doorway of spreadsheet aficionados. We can probably expect attractive presentation of data, as well as perhaps innovative and intuitive data entry solutions as Lasso's main selling points, while on the downside, the app's scope should be vastly limited in comparison to Excel (so that Microsoft feels warm and cozy and safe).

But in any case: iWork watch is on. It's unbelievable how much the world has fallen captive to the Microsoft Office suite. Shocking as it may sound, I think both Word and Excel are usability disasters, and the world would be a much better place if these apps did not have a monopoly. Most computer users in the world have resigned to the notion that a word processing document must be a Word document. Some less savvy computer users even wrap Word documents around images and ZIP files before e-mailing them, thinking that any document should be a Word document! Word is trying to be everything for everyone, and for a lot of people, it is everything. The poor devils. And while Word can do a lot, there's also a lot it does horribly badly, and frankly, just finding your way around that bloated beast can be a daunting experience.

It would be much nicer to have open document standards instead, and competing tools working with them. Hopefully, Microsoft's migration to open, XML-based document formats will help make that possible. And hopefully, one day we will see some real competition from Apple as well. Apple can do multimedia software and system software arguably better than anyone else. Office software should be somewhere inbetween, so Apple could excel there as well (no pun intended).

And by the way, I don't know how much of the user base realizes that the next version of Mac Office will do away with VB support. Microsoft Mac Business Unit development lead Erik Schwiebert explains very nicely how that decision was reached, and it ain't pretty. I'll give you the link to his blog, but be warned: the explanation will have you bang your head against a wall in frustration. Apparently VB support on the Mac was a lifesize model of the Eiffel tower built of matches, and it would all need to be dragged through the eye of a needle in order to be ported to Intel-based Macs. Microsoft says, "no can do." Not enough people. Yeah, right, you may actually read my comments on Erik's blog, so enough of that here.

What could be more ironic than having Apple come up with a way to implement VB in iWork? If Steve Jobs reads this, I think he will do it just so he can annoy Bill Gates. Just remember where you read it first.

Read More...