[size="4"][size=4][u][b]Why Online?[/b][/u][/size][/size]

Why am I developing my vending management software, VIKDR, online instead of for the desktop? Isn't a desktop solution what people have been requesting? Why would I seemingly ignore those requests?

Until now, I haven't adequately explained my reasoning, but I didn't just jump to the idea of putting VIKDR online. Before I even started, I spent at least 4 months thinking, researching, and planing what would work the best, would benefit the most people, and deciding if I was even capable of attempting such a project.

[size="4"][u][b]My Abilities[/b][/u][/size]

The last desktop programming language I really knew was Applesoft basic, (early 80's) and when I finally abandoned it, it was the older, out of date version of that language.

Over the years I have delved into HTML, and JavaScript, so when this project came up, my skills were already internet based. I had a head start for developing for the internet, whereas if I were to develop for the desktop, I'd have to start from scratch.

Since I was going to have to learn, and gain more skills if I was going to succeed, I wanted to make sure the skill sets I gained were marketable, and web development is more marketable then desktop programming skills, especially without the formal training, (i.e. no degree,) not to mention the fact that I find this form of development so much more interesting.

That wasn't enough to decide that online was the best choice, but it may have been enough for me abandon the idea if It wasn't. My research led me to a distinct conclusion that online was the way to go.

[size="4"][u][b]Decline of the Desktop[/b][/u][/size]

This may come as a shock to some of you, but the desktop computer is in decline right now. We're at the very beginning stages of it, and while I don't see it completely vanishing in the near future. There will probably always be a group of people using a desktop computer, but the general population is starting to shift away from it. Already people are abandoning the computers for cell phones, and tablets. Even companies that used to give their employees laptops are starting to give them tablets instead.

The idea of learning desktop programming made as much sense, to me, as learning VCR repair. It also did not make sense building a program that was going to be obsolete a few years after it was released. It's a mistake to design toward the past, I must design forward.

[size="4"][u][b]Cell Phones, Tablets, and the Mac[/b][/u][/size]

I also can't ignore that there have also been requests for a better online option, and still others looking for an app that works on cell phones, or tablets.

If I developed for Windows, I am ignoring the Mac users. If I developed a mobile app, which operating system? iPhone & iPad, Android, Rim, Palm, Windows Mobile? Would a mobile app even be powerful enough?

My research led me to a single solution that actually covered all bases fairly well, and that's...

[size="4"][u][b]The Cloud[/b][/u][/size]

This term is everywhere right now, and i imagine a few of you are already getting tired of hearing about it. But there is a reason everyone is talking about it. We are in the midst of a big technological shift, and there is no stopping, preventing, or redirecting it, and honestly we don't want to.

I found that I can build something that works better then a desktop application. Bold statement I know, but the plan is to have something that feels like your running a desktop program. At the same time taking advantage of the the power of the internet.

Naturally the release will come in phases, and phase II will involve adding in mobile friendly functionality. Something that will have a native feel on any mobile device, such as touch screen scrolling. It will seem to function like a mobile app, but because it is internet based, should work on any device with internet access, with the full power of the internet behind it.

The bulk of the processing power is moved to a server, with the sole purpose of running the application. This will give desktop power to the cell phone, and even some desktops will run faster this way.

My goal is to keep working on the application, and with customers, to produce the most powerful, functional, and ease of use program possible, at an affordable price. With constant evolution of the product, in a couple of years, it may look completely different then when originally released.

[size="4"][u][b]What about Privacy and Security?[/b][/u][/size]

I do find the worries about privacy a little overblown when it comes to vending. I'm not sure exactly how any of your stored information is going to benefit anyone else.

I doubt there are any Vendors attempting to hack websites so they can get other Vendor's information. It would be such a waste of time over actually running their business. And if there are, they must be a sad bunch.

But while I believe the fear is overblown, that doesn't mean I gave a short shrift to security and privacy concerns.

None of your information will be sold or traded to another party for any reason. No affiliate marketing, no third party spam. And I do not own, nor am I affiliated with a locating company.

The database used is fully HIPAA compliant. This means the security in place qualifies for the requirements set by the Government for the secure storage and privacy of medical records.

Now there will be some general statistics that will be shared for the benefit of members, but no specifics. There is some data will need to be shared with a third party to run the website, for example Google Maps. Other then that, all data will be kept confidential, and accessed solely for the purpose of website management.

At no time will specific data will be released to another entity without a court order.

Still there are times when a site goes down, or unforeseen glitches happen, so naturally I will maintain secured and redundant backups. Both in-house, and online. (There will be a minimum of 3 copies in addition to the original.)

[u][b]What about Hackers?[/b][/u]

This seems like a big concern with any online business. Many high profile hacking stories have been in the news recently. These are a little rarer then they seem, and having looked into this, I am in no way worried.

Hacking generally falls into easy targets, and big targets. Since there won't be any bank/credit card numbers stored on the servers, (the current plan is to use PayPal for financial transactions,) this really makes us a low priority target.

There is a kind of automatic hacking, where programs attempt to find weak links, commonly called brute force hacking. There are ways to put up roadblocks to short circuit the process.

Contrary to what they show in movies and television, the successful hacker rarely does it at his computer. Most successful hacking is actually a result of fooling an inside person into revealing key data. This can be prevented by following a protocol in relation to all data. But it doesn't hurt to be a small business where you know exactly who is allowed to have what information.

Some hackers have been brazen enough to walk into office buildings, find a computer that is logged in, and proceed to set up an account for themselves. But this only works in businesses large enough that a new face wouldn't draw attention. There are benefits to being small.

[size="4"][u][b]What if I don't have Internet Access?[/b][/u][/size]

Then how are you reading this?

To be serious, internet access is expanding and growing daily. Many people carry their modems with them, use their cell phone as a modem, or even to directly access the internet.

Many businesses maintain free internet access. I've parked outside a McDonald’s before just for the access. Some communities are starting to implement a free citywide internet. (Such as Corpus Christi.)

[size="4"][u][b]Software as a Service[/b][/u][/size]

My application is what's referred to as "software as a service". You are not buying the software, but renting access to it. The result is that the entry point for this software is much lower then if I sold it outright. (If I had to come up with a full purchase price, it would be close to 10 years of access.)

With software as a service, the motivation changes from moving a product to keeping customers happy. It's too easy to think that once a product is sold, the relationship is over. But with software as a service, I need to keep you happy, keep the software up to date, functional, and competitive.

I wasn't sure I was going to do this, but here is my pricing structure. I will be selling access in blocks of time:

[u][b]$25.00[/b][/u] - 3 month access. Good for the non-committed person.

[u][b]$45.00[/b][/u]- 6 month access. 10% cheaper then 3 months, convenient mid point pricing and access.

[u][b]$75.00 [/b][/u]- Full year access. $6.25 a month.

Obviously the full year is the cheapest and simplest way to go in the long run. I am offering the shorter terms to add some flexibility for people with different needs and desires.

Once released, everyone will be able to have a free month of access to test out the program. And that is full access. None of the annoying partial functionality, limits on data entry, or pop up messages asking you to buy the program. It will be just as if you purchased a month of access.

I am currently working on ways to gain "bonus" time. Ways that you can earn extra time for yourself. I'm not ready to reveal the details, just yet.

In the next few days I'm going to release an updated demonstration of what I have ready to go so far. It's still a work in progress, but moving along nicely.