SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Apple Inc. -- Ignore unavailable to you. Want to Upgrade?


To: slacker711 who wrote (69596)10/3/2007 3:37:10 PM
From: John Carragher  Respond to of 213182
 
Similar with ringtones" did yah,, get your Cramer ring tones?g



To: slacker711 who wrote (69596)10/3/2007 3:58:58 PM
From: inaflash  Respond to of 213182
 
I have yet to hear of a lawsuit by the RIAA of any of the other handset manufacturers.

Nothing really official, but lots of backchannel chatter...

How Apple Had to Backtrack on Ringtones
ipodobserver.com

Apple's iTunes Ringtones and the Complex World of Copyright Law
roughlydrafted.com

Apple, the RIAA, and Ringtones
apple.slashdot.org

I don't have an understanding of the legal issues or technical matters, and I've yet to see a Cliff Notes answer to the subject. I just know that the matter isn't settled and probably won't be for a while. Meanwhile, most handset makers don't have a strong short term incentive to rock the boat and be the ones defining the dividing lines. Why not make some extra revenue selling ringtones when everyone is doing it and pay the royalties instead of fighting a legal battle that might be lost and having to pay royalties AND legal fees and penalties? Once someone else has made the case, then change the system if it turns out to be ok. So, if Nokia wants to be a trailblazer here, let them do so (and piss off their mobile operators who are making the big bucks on ring tones). Meanwhile, Apple sits back and makes a few bucks on ring tones, and if need be, if deemed low risk, can open up the ring tone editor to the masses. Also, letting 3rd party hacks take the risk may be a passive way to get around this legal quagmire without assuming any liabilities.



To: slacker711 who wrote (69596)10/3/2007 5:23:58 PM
From: Stock Puppy  Respond to of 213182
 
My favorite phone as far as ringtones are concerned was a Nokia where you could program your own notes (or get the fake sheet and transribe... :-))



To: slacker711 who wrote (69596)10/4/2007 12:46:07 PM
From: slacker711  Respond to of 213182
 
Source: iPhone "SDK" will remain web-based for the foreseeable future

arstechnica.com

By Jacqui Cheng | Published: October 03, 2007 - 07:02AM CT

Apple is working on solutions that will help developers get more face time on the iPhone, but there are currently no plans to offer a "true" iPhone SDK that would allow developers to create native apps, a source at Apple has told Ars.

The company is currently planning a handful of updates to Safari and the iPhone that may appease some of the common complaints about developing for the device. For example, Apple is currently jamming on adding offline storage capabilities to Safari—something that would rival Google Gears in being able to serve up web applications locally without having to access the Internet. Our source says that the project is entirely for the iPhone: "The entire purpose of all this work is to make the iPhone 'SDK' (WebKit) more usable," our source told us. Because of this, the SDK will remain web-based, he said, with the applications remaining constrained to HTML, CSS, and a nice splash of lemon-scented AJAX.

That said, our source also believes there may be other goodies up Apple's sleeve. Apple may offer more local JavaScript access to useful iPhone functionalities, and developers might eventually also be able to create home screen icons that will point to their (presumably) offline web apps. Apple is currently aiming for an unspecified "January" deadline on these updates, and it doesn't take a rocket scientist to figure out that it will likely be announced at Macworld 2008.

All of this goes contrary to the long-held belief of many third-party developers, who have been praying to the Apple deities since day one that they'll have deeper access to the iPhone than a browser window. The news does, however, fall in line with information that we reported on last June from a different Apple insider, who said that he personally believed that there may never be a native SDK for the iPhone.

Given recent (non)developments in the hacking world when it comes to the new iPhone firmware and the iPod touch, things aren't exactly looking rosy for eager devs. Offline storage with the possibility of (Apple-sanctioned) home screen icons are certainly a major step forward, but it has its obvious limitations to the Web 2.0 world. "You can't write [bleep]ing [bleep] in that," says our source. Needless to say, even Apple insiders are not thrilled.

Our current source doesn't have any information on why Apple has chosen to continue to block out developers, but does have one theory. "Jobs is a control freak and doesn't want people messing with perfection." That's what we think here at Ars, too. Whelp, better get brushed up on those iPhone Human Interface Guidelines.