Graabein asks:
"I'm part of an effort to startup a VoIP provider. We've decided to use Open Source Software wherever possible. Production is not a problem, we can handle the VoIP network itself, POTS termination, web sites, email systems, all the usual stuff. The business side of things is another matter entirely. We need to be able to handle Customer Relationship data, manage subscriptions, handle invoicing and accounts, have a web shop of sorts, online billing, credit card transactions, and more. Whatever system we use has to be able to handle national standards for accounting, or at least be possible to modify to do so. We've looked at Compiere, but our business types are not impressed. Neither am I, for that matter. Requiring an Oracle license is one thing (database independence is 'in development', but it has been for a long time, with no discernable progress), not working properly with Mozilla is another (you need IE to use it fully in HTML mode). What other options are there?"
"Our business types are full of suggestions for supposedly excellent and well suited systems, however they all have in common that they require Windows on the client. If we choose one of those systems our OSS policy is pretty much moot and OSS has been relegated to (some) servers in the computer room and that's about it. I don't mind running these business functions on a Windows server if that is the best system for the job, but having to run Windows on every client in order to access the data is simply not acceptable.
We want Linux and OpenOffice on every desktop. We want to be able to access customer data from a variety of clients, even including Windows. The same goes for Accounting data, HR data, QA data, you name it. Do we have to write our own system from scratch? I'm not sure that is very realistic."
Slashdot Mirror
Simple answer: what you are looking for does not (yet) exist.
There are a lot of fancy applications on the net, none of them any usefull for your purposes (and please prove me wrong, I'd though I had been pretty thorough)
Having looked at the same problem for my own small business I'd say that if your business is essential to you, you either start asking for quotations for companies that can deliver a solution to fits your purposes or find a stock application that does most of what you need. (and does it in a way that most members of staff understand it)
Look at the price, and see if its matches your needs and budget.
As you are setting up your own business, you should NOT be fooling around trying to recreate the wheel; you will need al your energy to focus on your business and hope that it doesn't go belly up.
One sure way of doing that is having a dozen incompatible systems hide all your major business information from you, your customers, and your staff.
Don't count on a "web interface" equalling "will run on any platform". I've lost count of the number of "web enabled" applications that only work in I.E. Some vendors seem to think the purpose of a web interface is so you don't have to install new software on your Windows PC (giving them the benefit of the doubt vs just plain laziness/poor qa), whereas it _should_ mean it's platform and browser independent.
Personally, if it will only run on I.E. in Windows (wine/xover office notwithstanding), what's the point - may as well run a Windows app.
If a company goes to the trouble of making a web interface, it ought to be done "right", so any web browser that follows http/html standards can run it. It's not _that_ hard to do.
It's not the first $780 he's worried about, but the the 2nd, 3rd, 4th, etc.
IMO, browser-based interfaces lack in the usability front. They are simply not rich enough.
They work fine on the web because they are a compromise: I give you a site with a rather dull interface , but you get to it without installing custom software AND ALSO you are presented with a familiar and simple user interface (click links, scroll pages, fill up form fields, submit info), so you can catch on quickly with my site, because it work quite similarly to other sites you have visited before (an important aspect that some flash-based and some overworked DHTML-based sites seem to overlook).
Of course, the software used internally in a business has both more demands and less limitations.
It has less limitations because you can install wathever software you want (you have tech support, and don't depend on the end user failing to install the latest plugin). You don't have severe bandwidth limitations. You can standarize on a single platform for your clients, and on a single screen resolution (or, if it is not single, at least can be a known and definite set). You don't need to engineer your application to be run in a restrictive security sandbox, so you can have full control of the devices attached to your computer. For instance, you can make the application print an invoice as part of a transaction, without explicit user intervention (no "print" dialog), automatically selecting certain parameters (paper size, margins, resolution), not allowing the user to mess with them. The application you build can also have a steeper learning curve, because you won't have casual users (potential customers that have to figure out how things work on their own, and that you'll loose if they get annoyed), but permanent users that are your employees and can be trained.
The user interface of business software has higher demands too. If you fill in an online purchase form twice a week, you can put up with a clumsy user interface. But if that is your job, and you process purchase orders from 9 to 5, you'll need something better than the average HTML form. For instance, when a customer tells their name over the phone, you type the first three letters and a list of those customers that meet the citeria is instantly displayed for an easier selection. Also, you might want your text to be spell checked as you type when fou fill a text area. If you have used both SQL-Ledger and GNU cash, or PhpMyAdmin and mysqlcc, or any web-mail and any mail program, or groups.google.com and any newsreader then you should know what I'm talking about: even the best engineered web application falls short to almost all rich GUI applications.
Of course, in the future web interfaces might evolve to become richer (XForms, for intance), but until then, selecting a web-based architecture for internal business use certainly can hurt productivity.
Having said all this, I must also point out that it depends on what you call "a Browser-based application". I have taken for granted that the original poster meant a HTML-based application as opposed to, say, an application consisting in a single page containing a java applet or ActiveX control.