- Joined
- Jun 7, 2012
- Messages
- 74
Rep Bank
$415
$415
User Power: 77%
As some of you may know, I am a web app developer and am about 80% of the way through creating a website/blog/cms/e-commerce platform that will out-perform, out-feature and is much more flexible & easier to use than anything else I have seen (just some background so you know where I'm coming from).
I also sell products online and am about to release a new range of products that will require a typical online shop interface. These are almost ready to sell now so I decided to temporarily use a popular open source shopping cart & bought a decent looking theme for it with the intention of migrating to my system when it is ready.
The cart software was free, looks to be well written & works well (typical speed & ease of use issues aside).
The premium theme I bought has many rave reviews from its users & has generated revenue in the hundreds of thousands of dollars for its creator. (Note to self - write & sell themes.)
/** Rant start */
On inspection, the theme is absolute crap technically. I was simply stunned when I looked at the code.
It causes hundreds of html & css validation errors, contains many obsolete html attributes (even though I have the latest version which was released very recently), is very disorganised, completely un-commented, extremely bloated & ignores many coding best practice guidelines. In short, the product works and actually looks pretty good but the core is rotten.
/** Rant end */
I'm not at all concerned about this from my own usage point of view as it is only a temporary quick fix but it got me thinking:
Is it worth putting in the extra time, effort and expense needed to create a product you can be proud of or is it better to quickly throw something together for a quick profit even if you know it is rubbish as long as it looks ok & does the job? Not meaning being a perfectionist to the nth degree, just talking about a good, solid product.
In a situation where the customer probably won't be able to determine the difference which is more important - perceived quality (even if the product is poorly made) or real quality? Either way, why?
I'm not talking specifically about web related products - rather, any & all products (and services), physical or digital. I would be interested in all your thoughts & opinions about this either way from a business (not egocentric) perspective...
I also sell products online and am about to release a new range of products that will require a typical online shop interface. These are almost ready to sell now so I decided to temporarily use a popular open source shopping cart & bought a decent looking theme for it with the intention of migrating to my system when it is ready.
The cart software was free, looks to be well written & works well (typical speed & ease of use issues aside).
The premium theme I bought has many rave reviews from its users & has generated revenue in the hundreds of thousands of dollars for its creator. (Note to self - write & sell themes.)
/** Rant start */
On inspection, the theme is absolute crap technically. I was simply stunned when I looked at the code.
It causes hundreds of html & css validation errors, contains many obsolete html attributes (even though I have the latest version which was released very recently), is very disorganised, completely un-commented, extremely bloated & ignores many coding best practice guidelines. In short, the product works and actually looks pretty good but the core is rotten.
/** Rant end */
I'm not at all concerned about this from my own usage point of view as it is only a temporary quick fix but it got me thinking:
Is it worth putting in the extra time, effort and expense needed to create a product you can be proud of or is it better to quickly throw something together for a quick profit even if you know it is rubbish as long as it looks ok & does the job? Not meaning being a perfectionist to the nth degree, just talking about a good, solid product.
In a situation where the customer probably won't be able to determine the difference which is more important - perceived quality (even if the product is poorly made) or real quality? Either way, why?
I'm not talking specifically about web related products - rather, any & all products (and services), physical or digital. I would be interested in all your thoughts & opinions about this either way from a business (not egocentric) perspective...
Dislike ads? Become a Fastlane member:
Subscribe today and surround yourself with winners and millionaire mentors, not those broke friends who only want to drink beer and play video games. :-)
Access Restricted: Unlock 1,000,000+ Posts
Stop Peeking Through the Keyhole.
Open the Door.
You hit a wall because the best advice isn't free—it's earned. Since 2007, MJ DeMarco has been active here daily (99.9% active rate), building a war room for entrepreneurs who refuse to settle for mediocrity.
- Active Daily: Life-changing content posted dozens of times every day. No dead threads.
- MJ's Inner Circle: Direct access to the author of The Millionaire Fastlane.
- Vetted Network: Connect with founders scaling to 7 and 8 figures.
- Proven Roadmaps: Strategy over motivation. Execution over "hustle porn."
"SCALED TO 6-FIGURE MONTHS"
"Tips and advice here saved me from huge mistakes, others allowed me to scale my business to 6-figure months."— User MitchC
"INSANE QUALITY OF PEOPLE"
"The number of high quality people I've met from this forum has been insane. All of it predicated on building real value."— User Richard Peck
"You are the average of the five people you surround yourself with."
Are you surrounding yourself with success?
.
