Discussions

Hi!

It depends how big and complicated your e-commerce site is. Based on this, I'd suggest 2 options:

• if your needs are quite simple, I strongly recommend Snipcart (https://snipcart.com) & LocomotiveCMS. You can build and deploy an ecommerce website in no time. We've got an example here: https://github.com/locomotivecms/site-templates/tree/master/shop.
• if you have a build a big e-commerce site with complex invoicing/accounting, reliable product delivery system, ...etc, send me your email. One of our sponsors is building a top-notch and full e-commerce open-source solution based on Odoo (one of the biggest open source ERP) and LocomotiveCMS.

Hope it'll help you. If you've got more questions, email me at did at locomotivecms dot com.

Best,
Didier

There's also Ecwid which is amazingly simple to implement/customise.
The shop backend is outside of locomotive but it's a breeze to use and free for basic use but then you can buy extra features.
You can see a demo here (click on the shop link)
http://ecwid.studiowan.fr

This comment has been deleted

This comment has been deleted

Hello! Thank you for the great Information! I am now really eager to start my online store. Can you please tell me what are the charges that InstaMojo will take for using their payment gateway?
Regards
Ross Alisha

The fact that Magento is not even reviewed here completely discredits this entire video. Look to Forrester, Gartner, the IR500, IR B2B 300, IR1000... Magento is the best eCommerce platform out there for startups, $500M+ online businesses and everything in-between; the market serves as testament to that.
This post is targeted to people with a $2,000 budget who have a t-shirt idea that they want to take online. This is not for serious eCom.
Regards
Ashlay Jones

Wow! Thank you! I constantly wanted to write on my site something like that. Can I take a portion of your post to my website?
https://yourfavoritecrafts.com/

Thanks for your thoughts. Here are my responses to yours in turn: 1. I don’t think you’ve fully understood my point here (or I don’t fully understand your comment). The argument is as such – someone who browses to a site on their desktop/laptop, then browses to that same site on a mobile device, will be presented with a different design if it is responsive. That defeats the user’s expectation, and unless the design is executed extremely well, it can be a negative experience. 2. It’s got nothing to do with laziness – it’s about return on investment. It’s a business decision. Many people seem to consider responsive design a must-have without actually considering whether or not the extra time and cost involved is worth it. 3. That’s your personal preference – fair enough. I personally always view my browser in landscape. I’ll look at responsive designs and eBooks in landscape too, otherwise my eyes are constantly flicking from line to line. 4. I don’t think we disagree on this point. 5. With respect, I think you are browsing sites with your developer’s hat on, not as a user. The vast majority of users haven’t even heard of responsive design – if it’s readable, they’ll read it.
Joseph Donahue

We've developed 10+ e-commerces based on Locomotive + ShopInvader + ODOO you should have a look : https://shopinvader.com/

Implementing or not implementing a responsive design website should fall under the category “it depends”. Not every website needs to be responsive and each project should look at metrics before making a decisions one way or another. Apps are nice and have a purpose, but maintenance of apps will kill you in the end. Server logs and analytics should indicate the type of browsers and platforms visiting your site. The last project was an even split of desktop to mobile visitors with over 90% of all visitors visiting surfing a small group of pages. So why build two different sites for a handful of pages. If your client is planning to post URLs on billboards, transit and transit stops, then a mobile first option should be considered. RWD is really about building for ubiquity. We do not know the platforms or devices that will be used six months from now. But we do know that they will most likely have a web browser or browser based services. Responsive, progressive enhancement and adaptive design are all part of the evolution of delivering content. In the end, users are only looking for content. So realistically, we should be looking at a content first strategy. Give the users what they want and let the content be the same independent of platform. If you don’t, users will get the content they want using clipping services such as Instapaper or Readability.
Kelly Hubbard

Web designer programs like adobe web tools have a single platform which allows multiple devices interfaces(tablets, PC, mobile) all to be automatically created during design phase thus eliminationing any concern for redesign for each individual device as designer will have an over view about how information ids displayed and then decides whether this is what the wanted from the beginning

Harold Burton

Implementing or not implementing a responsive design website should fall under the category “it depends”. Not every website needs to be responsive and each project should look at metrics before making a decisions one way or another. Apps are nice and have a purpose, but maintenance of apps will kill you in the end.

Server logs and analytics should indicate the type of browsers and platforms visiting your site. The last project was an even split of desktop to mobile visitors with over 90% of all visitors visiting surfing a small group of pages. So why build two different sites for a handful of pages.

If your client is planning to post URLs on billboards, transit and transit stops, then a mobile first option should be considered.

RWD is really about building for ubiquity. We do not know the platforms or devices that will be used six months from now. But we do know that they will most likely have a web browser or browser based services. Responsive, progressive enhancement and adaptive design are all part of the evolution of delivering content.

In the end, users are only looking for content. So realistically, we should be looking at a content first strategy. Give the users what they want and let the content be the same independent of platform. If you don’t, users will get the content they want using clipping services such as Instapaper or Readability.
Jayme Silvestri

Thanks for your thoughts. Here are my responses to yours in turn:

1. I don’t think you’ve fully understood my point here (or I don’t fully understand your comment). The argument is as such – someone who browses to a site on their desktop/laptop, then browses to that same site on a mobile device, will be presented with a different design if it is responsive. That defeats the user’s expectation, and unless the design is executed extremely well, it can be a negative experience.
2. It’s got nothing to do with laziness – it’s about return on investment. It’s a business decision. Many people seem to consider responsive design a must-have without actually considering whether or not the extra time and cost involved is worth it.
3. That’s your personal preference – fair enough. I personally always view my browser in landscape. I’ll look at responsive designs and eBooks in landscape too, otherwise my eyes are constantly flicking from line to line.
4. I don’t think we disagree on this point.
5. With respect, I think you are browsing sites with your developer’s hat on, not as a user. The vast majority of users haven’t even heard of responsive design – if it’s readable, they’ll read it.
   Holly Hooper

The main issue (and this went way over most people’s heads, seemingly) is that most web designers are far too precious about responsive web design. It seems untouchable amongst certain groups. Whilst responsive design can be beneficial in certain circumstances, it is not a cure-all for web design across multiple platforms, and there are downsides to going responsive. It’s nice that you’ve highlighted that fact in your comment.
Paul Brown

This comment has been deleted

This comment has been deleted

This comment has been deleted

This comment has been deleted

This comment has been deleted