iTunes accounts hacked by ‘Texas Hold’em’ app
developer figured out a way to drain your balance with in-app
purchases.
http://thenextweb.com/apple/2011/03/01/apple-itunes-accounts-hacked-as-more-r…? GoToMeeting Invitation - BOSPDAUG Developer Group 7pm Feb 22nd
https://www3.gotomeeting.com/join/348119190 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Dial +1 (914) 339-0012
Access Code: 348-119-190
Audio PIN: Shown after joining the meeting Meeting Password: newton
Meeting ID: 348-119-190
GoToMeeting Invitation - BOSPDAUG Developer Group 7pm Feb 22nd
https://www3.gotomeeting.com/join/348119190 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. Dial +1 (914) 339-0012
Access Code: 348-119-190
Audio PIN: Shown after joining the meeting Meeting Password: newton
Meeting ID: 348-119-190
The iPad competition is almost here from RIM, H-P and Motorola - Chicago Sun-Times
http://www.suntimes.com/technology/ihnatko/3907834-452/the-ipad-competition-is-almost-here-from-rim-h-p-and-motorola.html
- via Feeddler RSS Reader
jab
It’s not Apple’s fault the publishing industry is screwed up
http://www.loopinsight.com/2011/02/21/its-not-apples-fault-the-publishing-industry-is-screwed-up/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+loopinsight%2FKqJb+%28The+Loop%29
What he said.
- via Feeddler RSS Reader
jab
Apple’s new subscription model— the 30% solution
- Marketwatch: Kindle hit hard: http://www.marketwatch.com/story/apple-subscription-deal-in-apps-may-hit-amazon-2011-02-15?dist=countdown
- NYT: http://mediadecoder.blogs.nytimes.com/2011/02/15/apple-offers-subscriptions-for-all-ipad-publications/?partner=rss&emc=rss
- TechCrunch: http://techcrunch.com/2011/02/15/apple-in-app-subscriptions/
- Paid Content: http://paidcontent.org/article/419-apple-subs-some-publishers-relieved-they-dodged-a-bullet/
- Jean-Louis Gasee (kind of likes it, who would have thought): http://twitter.com/gassee/status/37642355649675264#
- Rhapsody pulls out of the iOS world, goes to court: http://www.digitaltrends.com/mobile/rhapsody-wont-bend-to-apples-new-itunes-policy/
Sure to be a big topic of discussion at the next Bospdaug meeting this coming Tuesday February 22nd— for sure, you should be there either in person, or online!
Apple’s new subscription model— the 30% solution
- Marketwatch: Kindle hit hard: http://www.marketwatch.com/story/apple-subscription-deal-in-apps-may-hit-amazon-2011-02-15?dist=countdown
- NYT: http://mediadecoder.blogs.nytimes.com/2011/02/15/apple-offers-subscriptions-for-all-ipad-publications/?partner=rss&emc=rss
- TechCrunch: http://techcrunch.com/2011/02/15/apple-in-app-subscriptions/
- Paid Content: http://paidcontent.org/article/419-apple-subs-some-publishers-relieved-they-dodged-a-bullet/
- Jean-Louis Gasee (kind of likes it, who would have thought): http://twitter.com/gassee/status/37642355649675264#
- Rhapsody pulls out of the iOS world, goes to court: http://www.digitaltrends.com/mobile/rhapsody-wont-bend-to-apples-new-itunes-policy/
Sure to be a big topic of discussion at the next Bospdaug meeting this coming Tuesday February 22nd— for sure, you should be there either in person, or online!
What *could* Apple do for the next generation of iOS phones/iPads?
There are lots of rumours circling right now about a mini iPhone, a bigger screened iPhone, iPads with retina displays and small iPads.
It is, of course, quite possible that there will be no new iPhone/iPad mini, or iPhone Maxi or whatever. However, knowing Apple, if they do release a new class of iPhone or iPad, they will do so to make it as easy for the developer as possible to maintain compatibility. One thing that is a real obstacle for phone developers is a platform with devices varying their screen dimensions, processor capabilities and screen UI.
One thing we know for sure, is that any iOS will have the same UI (excepting the AppleTV2), so that isn’t an issue here, but no developer wants to go back to their code and re-work it AGAIN. Remember, the release of the iPad and iPhone 4 gave the developer two new screen sizes to work with and all sorts of OS changes.
Now, with the iPhone’s retina display being twice the resolution of the original iPhone screen, that made it easy for developers. The choice was modify your code to take advantage of the higher resolution screen or be lazy and let iOS do the job for you. With the iPad, extra thought has to go into the total application layout as the screen has so much real estate and you have to think more about device orientation.
Which leads me to a conclusion that could be on the money or totally wrong - only Apple knows for sure.
If, and I do stress the * IF * bit, Apple release an iPhone Mini (which I think is likely at some time, as it will mimic the rollout strategy of the iPod), then I suggest that the screen could be a retina display that is the same resolution of the iPhone 3GS (though I admit that the device could be too small).
If we get an iPhone MAXI, then I suggest that the screen would be a retina display with the same resolution as the iPad.
There could be other options using this idea, but you get the gist.
I do appreciate that the actual device sizes we get out of this process might be sub-optimal, but the reasoning of the process is still sound in my opinion. Apple wants to make life as easy for the developer as possible and to inflict real pain only when necessary. I don’t think that the product life cycles of any iOS device is at a point where there will be significant change (like the jump from 3GS to 4), so I don’t see Apple making life too difficult for it’s developers.
TTell us in the comments what you think.
Motorola, you wish
Sent from my iPad
Page 1 of 11
