One Page Checkout : Should we have to pay for it?

[Richnyc30]

The problem is the war (between Facebook and Google, for instance) for programmers is causing real problems for projects. It's making everything expensive and generally a problem for good code.
We can only hope things don't get too expensive around here and get finished.
Richard

[benjamin]

Alkaline,

I like how you guys set up the 4mdmedical.com 1-page checkout. How much do you guys charge for that 1-page checkout solution?

Thanks,
Ben

[benjamin]

BTW, I agree with BFG 9000 on the point that Vortx should get the existing ASPDNSF 1-page checkout working, at least in its current form.

The solution that Vortx built before as a plug-in, they can keep that separate. But at least fix the bugs in the built-in 1-page checkout in v9 so it's functional without bugs. The way it currently is, it's very buggy. Since that page is included in the overall product, its unusable status makes the entire package basically unusable if someone is looking for an e-commerce solution with 1-page checkout.

At least if it's bug-free, people can use that page to start with and decide to upgrade to a better 1-page checkout as they build out their site.

Just my 2-cent.

[Richnyc30]

The problem with all this addins and other things, especially monthly issues bring back the terror of someone's server going down and the system stops as the addin tries to call home. It's a bad thing.

[sduffy77]

BTW, I agree with BFG 9000 on the point that Vortx should get the existing ASPDNSF 1-page checkout working, at least in its current form.

The solution that Vortx built before as a plug-in, they can keep that separate. But at least fix the bugs in the built-in 1-page checkout in v9 so it's functional without bugs. The way it currently is, it's very buggy. Since that page is included in the overall product, its unusable status makes the entire package basically unusable if someone is looking for an e-commerce solution with 1-page checkout.

At least if it's bug-free, people can use that page to start with and decide to upgrade to a better 1-page checkout as they build out their site.

Just my 2-cent.

I agree! Can we get a response from Vortex?

[mlogan]

I bought the cart almost 8 months ago, on either side of the VortX purchase ... and have been setting the actual a business up and am now getting back to making the site w/ SP1.

I've notived many changes ... the left nav issue, being in the source code (I think, which I don't own), the mobile browser issue which was one aspect that moved me towards ASPDNSF, and one page checkout.

It appears to me that Vortx is just going to leave the cart as is, and then charge for add ons (with a recurring fee no less). If I hadn't already purchased the cart, I'd would certainly look elsewhere, and am considering moving before getting to invested, as I see the direction this is going. I will surely tell others to look elsewhere.

[wkeithg]

What I've found is if you've modified your site at all, e.g., added a shipping method, it's going to be tough to get it to work with the plug-ins since you don't have the source code for them. It'd be great if they came with an API or some such to better accommodate non-vanilla site implementations.

[Kev]

The checkout that comes with aspdotnetstorefront is truly the worst checkout I have ever seen. I wonder how many stores would see their conversion rates go up 25% by switching to a cart with a checkout system that wasn't last updated in 1998?

[walkinwillie]

I believe that if one-page checkout is advertised as a feature, then it should work and work well like the rest of ASPDNSF does. There shouldn't be a need for third party add-ons for advertised features. IMHO, third party add-ons are for functionality not presently included in ASPDNSF. I'm not real thrilled that a product advertised as "Multi-Store" in its title makes you pay extra to well....um....add more stores.

I've never been a fan of "per domain" software licensing. When I bought the ASP.NET AJAX controls from Telerik, I can use them on as many websites as I want - and like ASPDNSF, it is website specific software. The only difference is that ASPDNSF is narrower in focus (i.e. only e-commerce while Telerik controls are used in all types of websites) so I guess that is why ASPDNSF does the per domain licensing.

What I think ASPDNSF has to be careful about - and this was touched on by another poster - is shrinking the functionality of the core store and moving previously available functions to their own add-ons or third party add-ons. Right now, there is not another add-on - either from ASPDNSF or another company - that I really, really NEED. Sure, a Google Sitemap Generator would be nice but we have product feeds so I really don't NEED that add-on.

I can imagine that ASPDNSF has a lot of discussions about this topic. I know I often wonder what ASPDNSF's e-commerce market penetration is like - i.e. is there a lot of market share yet to be taken or is the market getting saturated? I know that ASPDNSF is not for everybody - you have to know some server stuff to install this software (and own more than just a little web development skills to customize the look) - and a lot of Mom & Pops won't spring for those kinds of installation services (even when it would be very financially prudent to do so) so that is a market share barrier.

Anyway, my $0.02 worth (if worth that much....)