HTTP Reviews

Shopify Reviews

1. Beard

   almost 3 years ago
   Shopify - the best no code platform.

   Creating my online store for small dog products on Shopify was a remarkably smooth and rewarding experience. Shopify's user-friendly platform guided me through each step of the setup process, making it easy even for someone without prior experience. Their range of customizable templates gave my store a professional and appealing look, and the analytics tools provided have been invaluable for tracking my store's performance and customer trends. Additionally, Shopify's 24/7 customer support was always ready to assist whenever I encountered any roadblocks. Overall, launching my business on Shopify has been a positive experience, and I would highly recommend it to anyone looking to start their own online store.

   🏁 Competitors: Tilda, WooCommerce
2. Lori Appleman

   · Founder at Redline Minds · almost 6 years ago
   Strong Option for New DIY Stores Serving Consumers

   Shopify is a powerful marketing machine that has driven incredible growth. It's an excellent choice for the store owner who needs to do it themselves, on a shoestring budget, who does not sell complex products and who does not plan to run a hybrid - a store that serves multiple customer bases such as retail and wholesale.

   Due to its sheer market share, there is a robust marketplace of apps that can be added to shape the store to fit most needs. There is an equally robust selection of themes and developers who can assist with any size project. They have a terrific knowledge base which I strongly recommend store owners use as it teaches the basics for e-commerce in general and online marketing. This learning should be done prior to developing a plan for your site. That will help root your project for success.

   Unfortunately, it's also oversold based on name recognition even when the platform is a poor choice for a specific business. There are both policy and technical limitations that impact suitability.

   Shopify stores require many apps, which adds monthly costs and can greatly slow your store down. While ALL online stores end up with some app use, because this allows you to choose the features you want and need, much of what is native in other carts like their most direct competitor, BigCommerce, is not. So you'll spend more money each month and it can be harder to get a fast site.

   Among the stores that should probably NOT use Shopify: - Sells items that are generally prohibited on the platform which includes weapons, weapon-related items, sex objects, tobacco (for some odd reason Vape is currently on the platform but for how long is anyone's guess), alcohol.
   - Sells items allowed but that don't qualify for Shopify Payments which expands the above list to include supplements, CBD, vape products and other items. - Just as above, any store that can't qualify for Shopify Payments or who has good reasons to use another payment gateway. Why? Because if you don't use their payment gateway which they profit from, they will take 1/2-2% of your gross revenues soley because you are using another gateway. For small merchants, this isn't much, for big ones it's a significant cost. - Stores with multiple price structures or catalogs - such as those who offer VIP tiers or wholesale clients. Why not? Because you can't create true customer groups which on other platforms let you segment the catalog and content for each customer group. Groups are really important for B2B. To accomplish multiple audiences on Shopify requires either a separate app (at an added cost) or multiple storefronts, or ShopifyPlus (which is still creating multiple sites). This can greatly increase your operational costs and work efforts. - Stores with complex products - these are items with many options, also known as configurable or customizable products. While Shopify does offer the ability to offer up to 3 options per product with a maximum of 100 skus per product, this limit is very easy to exceed. There is also no native path to add modifiers such as those one would use for personalized products (like custom embroidery. While these issues can be overcome with apps, that adds both load time and costs.

   🏁 Competitors: BigCommerce, Magento, Miva, WooCommerce, Workflow

   👍 Pros:    Easy to use|Low price|Flexible|Large developer base|Great documentation|Reliable|Low maintenance

   👎 Cons:    Limited features|No customer groups for wholesale|Some product types forbidden|Must use their gateway or pay extra fees|Limited api calls|Limited capabilities for products with options

HTTP mentions (9)

• The History of HTTP

  HTTP/1.1 was first published as RFC 2068 (The Proposed Standard) in January 1997. HTTP/1.1 protocol was refined over two revisions, RFC 2616 published in June 1999 and RFC 7230-RFC 7235 published in June 2014 before the release of HTTP/2. The HTTP/1.1 standard (RFC 2616) remained stable for over 15 years. In 2022, HTTP/1.1 was updated again with RFC 9110 & RFC 9112. - Source: dev.to / 9 months ago

• State management in Svelte apps

  HTTP was invented as a stateless protocol, which means that each request fully encapsulates all of the information necessary to return a correct response. So historically, web pages never had to worry about managing state - each request to a URL with parameters or with a form submission would receive a response with all of the HTML that the browser needed to render content. - Source: dev.to / about 2 years ago

• Evolving the Web: Discovering the History of HTTP Versions

  HTTP/1.1 was such a game changer for the Internet that it works so well that even through two revisions, RFC 2616 published in June 1999 and RFC 7230– RFC 7235 published in June 2014, HTTP/1.1 was extremely stable until the release of HTTP/2.0 in 2014 — Nearly 18 years later. Before continuing to the next section about HTTP/2.0, let us revisit what journey HTTP/1.1 has been through. - Source: dev.to / about 3 years ago

• Poll: Are client web requests sent to upstream servers or downstream servers?

  On the one hand, it just seems natural that "upstream" refers to the inbound request being sent from one system to another. It takes effort (connection pooling, throttling, retries, etc.) to make a request to an (upstream) dependency, just as it takes effort to swim upstream. The response is (usually) easy... Just return it... hence, "downstream". Recall the usual meaning of "upload" and "download". Upstream seems... - Source: Hacker News / over 4 years ago

• How to cache TCP, SSL handshake on ALB?

  To me it sounds like you’ve not solved this as the config you’ve mentioned is about preventing “illegal” (none RFC7230 ) requests, it isn’t really related to the problem you posted. Source: over 4 years ago

Shopify mentions (44)

• Material 3 Expressive: Better, Easier, Emotional UX

  I don’t think is ugly, it is just that it feels like every trendy company webpage copied and pasted the same design: http://shopify.com/. - Source: Hacker News / about 1 year ago

• 11 real-life PWA examples you can learn from in 2025

  Shopify is one of the easiest platforms for selling products online, and turning your store into a PWA with installation and push notifications takes just a click, thanks to the Shopify app store. - Source: dev.to / over 1 year ago

• shopify.com vs store.link, what do you think is better one?

  Shopify.com vs store.link which one is better? Source: almost 3 years ago

• Forget Shopify Why MedusaJS Is the Future of Headless Ecommerce

  With a traditional e-commerce platform like Shopify, you're locked into their ecosystem. You have to use their templates, checkout, and backend. Headless platforms like MedusaJS give you the freedom to build the front end however you want, using any framework or library. - Source: dev.to / about 3 years ago

• Allow Rules not given priority over block?

  For example, if you want to load firewalla.com, just allowing "firewalla.com" will not work, you will have allow shopify.com and few other stuff ... You can see what sites loaded using chrome dev mode. Source: about 3 years ago