Webstore back-end on site or on desktop?

Question

1.00/5 (1 vote)

See more:

Background
I've been tasked with making an online store for a company, due to them being a B2B company, they are less in need of some webstore CMS, and more after a system to be reliable and user-friendly.

Since my focus has been on .net for desktop and PHP for web, (and I am forced into using ASP), I was thinking of doing something I've done for my own webshop, which is creating a desktop interface for handling the orders, editing items, etc. I did this so I could have the desktop application running in "minimized to tray" and get notifications on my computer.

Question
Is a desktop-based back-end a good idea? I want to do it, but I want some input before I make a prototype show it to my customer. I am mostly looking for "problems I have missed" feedback, but any would be nice

Aside:
The logic behind the desktop-backend is that the customer will be wanting a way to handle shipping, and maybe not be bound to be on the internet at any given time.

thanks!

-Frank

Posted 2-Jul-14 6:29am

Frank R. Haugen

Add a Solution

Comments

Sergey Alexandrovich Kryukov 2-Jul-14 14:04pm

ASP.NET is not ASP...
How a desktop-based back-end could be a valid idea at all? Are you going to self-host it as some Internet service? But then how it's different from a server? And the case when something is not connected to the Internet? Well, one can work off-line for certain operations, but is the whole business is based on Internet, well... then it is based on Internet...
—SA

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)