[superxor]

I once used Quickoffice on a Symbian S60 phone. I should say, it's capabilities were pretty impressive. Especially with the meager resources available on those old so-called smart phones.

I hope this helps Google build better native Office apps. Obviously, will also be a big addition to their Docs back-end. But it has always puzzled me, with the infinite resources Google has, it still has not been able to develop a seamless import of MS Office files. Is it really that hard?

[hesdeadjim]

Having worked at Quickoffice years ago on the spreadsheet team, I can tell you that yes, it is really, really hard to do well.

People expect when they open their spreadsheet that the formulas they wrote on the desktop will provide the results they see on the desktop. Ok, well it's just math right? Yes, and no. Excel actually has a lot of bugs with the execution of their formulas, so to be accurate you have to emulate all the mistakes they make. You also have to discover these bugs yourself, as they are not conveniently documented somewhere.

I ended up writing a unit test framework using generated Excel spreadsheets containing permutations of formulas with every possible input, just so I could identify where these bugs might be happening. Then you have to reverse engineer WHY they happen in the first place, and also find out if this was something the Excel team fixed in later releases, or left in because they themselves could not break backwards compatibility.

And this was what I would consider a small problem for us back then. The biggest problem was always round-tripping of unsupported data. The Office file format is large, complex, and full of crap you wouldn't imagine supporting in a mobile product. However, your users expect that if they open a spreadsheet to change a number on their phone, when they save it and re-open it on the desktop all the fancy formatting and pivot tables still work and haven't been lost.

Anyways, this is a great purchase for Google and I congratulate all the guys who have put in the hard work to make Quickoffice the amazing product it is today.

[snewman]

Yeah, it's pretty hard. Microsoft's spec (for the OOXML formats) is over 6,000 pages long, and extremely hard to follow by all accounts. And no, that's not a 10-page specification followed by 5,990 pages of examples. The Office apps have incredibly complex functionality, and then factor in decades of revisions, upgrades, overlays, and general complexity creep.

Also bear in mind that while Google does have large (not infinite!) resources, they also have large responsibilities. Like anything, it comes down to economics: they could hire or repurpose 500 engineers to work on Office file formats, but it's not the optimal thing for them to do.

[enjo]

Keep in mind, Quickoffice (I was there) did that before the spec was released:)

[Create]

Sun did it back to improve StarOffice, though with only a few.

[lukeschlather]

Does Microsoft have seamless import to 365? I honestly think it's not just hard, it's impossible. There are always going to be formatting glitches that creep through.