Google's lax vetting allows almost any app in the Android market. Unscrupulous developers rejoice.
It collects a user’s browsing history, text messages, your phone’s SIM card number, subscriber identification, and even your voice mail password. It sends the data to a web site […] That site is evidently owned by someone in Shenzhen, China. The app has been downloaded anywhere from 1.1 million to 4.6 million times.
Though the research comes from a maker of Android security software, they've identified what the malicious app does and where the data is sent; the issue is real.
No vetting is perfect. Apple recently approved a flashlight app that housed a tethering application (though it harmed no users). But Apple shows concern about iPhone privacy. The excellent location services in iOS 4 are a great example. I appreciate the work they do on this.
For Android, we can and should excoriate the developers of this particular app, but we should also excoriate Google for barely trying to avoid this sort of thing.
So this is Android:
- Available apps with little curation, and security issues being exploited.
- Multiple OS releases and features that may or may not be coming to your particular hardware.
- Multiple devices from multiple vendors each having vendor-specific software/services (crapware).
- A real possibility that soon running security software will not only be prudent, but a foolish thing not to do.
Do these sound familiar? It's the Windows OS model of the 1990s. Android resembles it more every day.
Perhaps the most important stat from Validas's wireless smartphone bill analysis
But, more than 4 percent of VZW Smartphones consume more than 2 gigabytes per month, as opposed to just 1.6 percent of iPhones.
That's it right there.
Remember when AT&T introduced their data caps? The highest cap was set at 2GB, and there was outrage. AT&T said only 2% of their customers use more than that each month, but few believed them. Well, it's just 1.6%.
I dropped two iPhones on our family plan to the $15 200MB cap, and mine to the $25 2GB cap. That's $35 a month saved with no decrease in activity on our part.
The caps work, and they save you money. Lots to complain about AT&T for, but not everything they do is evil. This one's putting money in my pocket, and would do the same for 98.4% of you.
Apple's New Magic Trackpad: A MacBook Feature Comes to the Desktop [u]
Thoughts On Today's Ruling About "Legal" iPhone Jailbreaking [u]
First, Jailbreaking was never really illegal. If legality is what kept anyone from doing it I think they were misinformed. It was a gray area awaiting a ruling either way; Apple wanted the court to settle the question as to whether jailbreaking violated copyright, and they did, though not in Apple's way.
There is zero evidence to support Apple would have gone after individual jailbreakers (had the ruling gone the other way), any more than they go after one-off Hackintoshers.
I believe Apple wanted the shield of illegality not to go after geeks, hobbyists, etc., but rather to stop the unscrupulous who may now crawl out of the woodwork to make a quick buck on this.
I can practically see "Jailbreak Kits" for sale already. Their marketing copy gushing about how this once forbidden activity is now available to the general public. They'll publish a link to the Library of Congress statement that few will read and fewer will understand. They sure as heck won't dwell on the practice being unsupported, or that the next iOS release will likely kill it. Money in hand, they're off to the next sucker leaving their current "customers" yelling at Apple as if it's Apple's fault.
Finally, Apple will continue to "break" jailbreaks. Not only does the statement not mean Apple must allow the activity, but I believe every jailbreak so far relies on a security exploit. Of course Apple's going to plug that hole. They better.
[UPDATE:] See this excellent post for more information what today's copyright ruling really says.
Dear Apple: Only 235,000 Apps? Only 47,000 Developers? Your "Closed" Model Sucks.
Total Active Apps (currently available for download): 234,915 […]
Number of Active Publishers in the US App Store: 47,370
I'm surprised Apple hasn't shut that site down for regularly publishing Apple's shame.
Meanwhile, I'm certain Android's freewheeling, "open" (except for the native API, or Flash), look-the-other-way, Lord of the Flies approach to app development has resulted in numbers that embarrass Apple's.
Right?
And even if the numbers aren't quite as high, I'm sure Android apps are overall of a higher quality, and will run on a higher percentage of phones than Apple's.
Right?
And even if fragmentation is a bit more of an issue, I'm sure Android developers are raking in cash from the reported 160K activations (potential new customers) per day.
Right?
For shame, Apple. Don't you know "open" always wins?
Steve Jobs comes back to Apple and we all know what happened. Michael Dell comes back to Dell and, wow.
The SEC says that the company should have disclosed to investors that it was drawing on these reserves, but did not. And it claims that, at their peak, the exclusivity payments from Intel represented 76% of Dell’s quarterly operating income, which is a breathtaking figure.
It's bad enough Dell never did particularly well after Dell's return, but now we discover it would have been even worse had it not been for "accounting shenanigans" through the use of "cookie-jar reserves" made up of Intel's money.
iPhone Developer Shows One Way To Handle An App Store Rejection
Options…
- become enraged at the fact that Apple has the audacity to reject us for knowingly using code that violates our developer agreement then alert the media in hopes that everyone will be sympathetic to our plight especially Gruber (be sure to link to a post of his saying that he was right about something because we all know that that’s the easiest way to DF linkage) then write Steve Jobs a letter and sulk at his inevitable response where he doesn’t bend an inch then bitch-quit the App Store (only to return with tail between legs 6 months later)
- just remove the illegal feature and submit again
The above is from a post about getting Camera+ approved for the App Store. The app had just been rejected, and it's their description of the two options they felt they had.
They chose the second one, by the way.
The result? Not only is Camera+ in the App Store, it recently received a killer update and I believe is now better than Best Camera. (Like Camera+, Best Camera was designed with a photographer to make it easy to shoot, edit, and share photos.)
So whether you appreciate the Camera+ developers and photographer for focusing on getting their app to market instead of complaining, or simply because they have a great app, you should check it out.
Finally, I know there are App Store rejections not so neatly dealt with. That's all the more reason to highlight Taptaptap's actions. The complaining from those who could just follow the rules tends to drown out those with legitimate issues who don't have such a clear option.
In The Face Of Android's Success, Perhaps Its Best Phone Dies
Google warned potential customers last week that it was close to discontinuing the Nexus One, and this Android OS smartphone didn't last much longer -- Google has sold its last unit.
Against the backdrop of recent reports about impressive Android sales, perhaps the platform's best phone, the Nexus One, has been discontinued.
Though released a few months ago, the Nexus One's specs are still impressive. A 1GHz processor, 800 x 480 AMOLED screen, 5MP camera, etc. It was certainly not canceled for being out of date. But I'm not interested in phones just for spec geeks—the sum of the parts is what matters—it's the non-geek areas where the phone is more impressive than its flashier peers.
While many Android phones are getting bigger, the Nexus One is a relatively compact, smooth phone that fits well in the hand. The design is low-key, and in my opinion looks better for it.
And then there's the distribution. The phone was sold direct, either unlocked or with a contract for T-Mobile or AT&T, and was unencumbered by any of the carrier or manufacturer add-ons we see creeping into the Android world.
In comparison to many new Android phones, the Nexus One:
- Did not include third-party carrier or manufacturer "crapware"
- Did not include a third-party UI, such that another Android user may not even recognize it
- Represented a "clean" Android install
- Can install the latest Android release (2.2)
That last point is interesting. Android phones released even in the last month (e.g., DroidX, Galaxy) are running Android 2.1. The addition of third-party UIs, software, and carrier requirements make testing an OS release more time-consuming. These phones will likely be certified for 2.2 at some point, but by then that release may be old news. Nexus One's "clean" nature made new release certification a relatively speedy affair.
I don't think the Nexus One cancelation had anything to do with design, hardware or software. Rather, I think it was a victim of its own distribution. Buying online with little chance to touch/feel the phone hurt it. Out of sight, out of mind. It was also a victim of Google being wholly unprepared to deal with client support issues. The decent buzz it had at the beginning was soon crushed by bad buzz about support.
I wish Google had done a Nexus Two, but I understand why they did not. Google's interest in Android is to get it in as many hands as possible and sell ads. In Google's eyes, a Nexus Two would provide no advantages to them or their ad buyers over any other new Android phone. The fragmentation of varying UIs, services, and other add-ons doesn't need to concern them. Sheer volume and ads, that's their business model. I'm not knocking the model (it's very successful), but it's in keeping with it that they not waste resources on another Nexus.
Pity, though. I think Google inadvertently showed everyone the best way to make an Android phone.
AT&T Needs A Map For That
Meanwhile, somewhere in Michigan, an iPhone owner is invited to the AT&T store a mile from my California home.
Home Sweet Home (Screen)
As of right now, and always subject to change.
