edit-article

Article Name:

Article Description:

Chapter ID/Name:

Status:

Add Photo:

Owner ID:

Content: use HTML Edit Content

<h1 style="text-align: center;">tie in to msft operating system</h1>
<h2>[WHAT]</h2>
<ol>
<li>] Have you ever heard someone say "i can't switch from my iphone because i bought all these songs thru itunes ... " OR " i bought all these apps". They believe that they are tied to one manufacturers ecosystem because of the *content they purchased* thru that mfg's ecosystem.</li>
<li>] If at some point in time, the consumer decided that they wanted to use another mfg's device to play the *song that they purchased*, they are SOL.&nbsp;They didn't really buy a "song" they bought an "isong" that only works in "iworld". The&nbsp;mfg(AAPL) has successfully "tied them" to using their products and their services exclusively.&nbsp; </li>
<li>] This is not to pick on apple(aapl) or to paint microsoft(msft) with the same brush. windows-8(w8) is offering a lot of additional msft services through their core os product. Depending on how msft "plays this game", could turn out to be a big PRO or a big CON for the os and the company.&nbsp;Offering value added services to the consumer is a PRO, but tieing&nbsp;consumers to using your&nbsp;products/services exclusively, not so much.</li>
<li>] Given&nbsp;msft's "track record" and the percieved "level of trust" that&nbsp;they have in 'the community', i've listed&nbsp;it as a potential con for now ... - personally to date, i have only seen a few items(EX 1 ads in native apps ) that have raised any concerns. </li>
</ol>
<h2>[WHY]</h2>
<ol>
<li>] why do i need/want/use this [what]</li>
<ol>
<li>]</li>
</ol></ol>
<h2>[WHERE]</h2>
<ol>
<li>]&nbsp;to use [what]</li>
</ol>
<h2>[WHEN]</h2>
<ol>
<li>] to use [what]</li>
</ol>
<h2>[EXAMPLE]</h2>
<ol>
<li>] what in action</li>
</ol>
<h2>[HOW-TO]</h2>
<ol>
<li>] getting started with [what] step-by-step</li>
</ol>
<h2>[REFERENCE]</h2>
<ol>
<li>] sources</li>
</ol>
<p>&nbsp;</p>