dream product linuxcon europe europe
TRANSCRIPT
Description
What and why OSV vendors should do to keep OEMs and their customers satisfied for a long period? How to develop a new product which will become trendsetter?
Balanced products with polished hardware and optimized software well fit together are still a rare sensation on the market. There are a few companies who managed to get them on a regular basis and most of them are proprietary vendors possessing and controlling both hardware and software development.
This presentation will provide an overview of mission critical elements required to successfully cooperate with computer OEM companies in order to develop a “Dream product”.
How to Develop a Dream Product: OEM and FOSS OSV Synergy.
Dmitry Komissarov ROSA CEO and co-founder
LinuxCon Europe, November 2012
What is a Dream Product?
It might be unique…
The first satellite had been sent to space on October 4th,1957
What is a Dream Product?
It might be mass production…
What is a Dream Product?
It might be mass production…
70 000 000 pcs had been manufactured over the last 60 years
What is a Dream Product?
It might be adored or hated…
“…There's no chance that the iPhone is going to get any significant market share. No chance. It's a $500 subsidized item…” Steve Balmer, CEO Microsoft
What is a Dream Product?
But anyway Dream Products lead to
• Economy/Technology/Lifestyle BREAKTHROUGH!
• Deeper level of comfort/satisfaction/effectiveness.
• Fast growing ADDICTED customer/fan base.
• Lot of fun and aspiration for developers.
• (Might be …) profit .
Current Environment
• Fast pacing electronics development requires ASAP Time to Market.
• High RnD budget luxury is concentrated in the largest multinational companies (MS, Google, Apple). This results in a limited software platform choice and thus little chances to differentiate.
• Economics issues cause slow market growth.
• Evaporating margins for hardware vendors.
Consequences…
Apple $600+ Bn
HP
Samsung
Lenovo
ZTE
DELL
Nokia
Sharp
Sony
Common OEM/OSV Issues
OEM
OSV
Market ExpectationsWho's guilty here and who is right
Is not for us to say. But anyway the cart's still there today.
Common OEM/OSV Issues
Hardware vendor: “I do not care much about software. It should just work perfectly on my new shiny device. By the way …. you got 2 months to develop custom OS for me.”
Software vendor: “Why do they use this crappy components with no appropriate drivers? Why that system is not designed for my software?”
Developers: “We want fun. Documentation and QA are boring.”
Design: “Frankenstein”.
Security: Weak and last minute hardware and software integration leaves holes for intrusion.
Result: Complaining consumer will try his fortune with another device “designed in California”.
Linux specific OSV/OEMs issues
• Linux is free… at least very cheap
• Device drivers… Who cares?
• “Why it does not look like Windows, (Mac)?”
• We’ve heard about KDE. We want it on this 6’’ touch screen.
How Dream Products Evolve?
“Genius is one percent inspiration and ninety-nine percent perspiration.”
Thomas A. Edison
Product Life Cycle
Concept Creation
• Shared vision • Joint research process
and ideas pool• Commitment to
collaborate• Trust
Concept Development
• Joint and mixed design/engineering/marketing teams
• Diffusion of hardware and software technologies to achieve balance and synergy
Market Development
• Common business incentives• Joint marketing• Seamless services integration
Market Development
• Common interests• Clear communication• Highly coordinated execution
A Dream Product. How To Make It Happen?
• Early engagement in new product concept development. Make sure OEM and OSV shares a common vision and goals.
• Trusted relations. Clear communications.
• Executive buy-ins and sponsorship from both sides.
• Joint (SW+HW) Design, Engineering, Sales and Marketing teams.
• Open standards compliance.
Financial aspect
Common practice today is:
$$$ Total OEM2OSV =
NRE + Per unit fee * Number of Units sold.
…but
High Non Return Engineering (NRE) payment distracts OSV from business success.
Shared risk (higher Per unit fee, less NRE) motivates for better performance.
True Collaboration Example
Open Design Initiative
Open Hardware: Open specifications, Early planning stage access
Open Source Software
Open and Common Standards
Better Products and Happier Customers!
+
+
=
+
+
=
Summary
• Dream Product development requires high OEM and OSV integration from the earliest stage of products development.
• Common and open standards foster better and easier collaboration.
• In order to achieve higher effectiveness, we need to embrace OSS principles to whole product development.
• Open Design Initiative might serve OEMs and OSVs to create Dream Products.
