When some people (like PC World) come up with lists of “What iPhone OS 4.0 Needs” they often lists items that are not thought about from a design direction at all.  They think of a task they want to perform, look at a previous solution for that task, and proclaim that the same solution is needed here. (To be fair, PC World does not invoke as much Fire & Brimstone as others who deliver this opinion.)

We don’t need a floppy drive on the iPhone.  No one is suggesting we do, but it was only a few years ago that people were wailing for their loss on a computer (How do we manage to install new software without them?).  Now people often state they need access to the underlying file system of their iPhone.  Their phone.  They need to get to the filesystem.  And browse it.  Why? why? why?

With the announcement of the new iPad running a newer version of the iPhone OS, no doubt these statements will grow louder.  Access to the filesystem oddly makes a lot of people’s lists.

OS X provides the Finder to me, and it provides Terminal to me. I’m sure my mother doesn’t know what Terminal is, and I know she’s not overly familiar with Finder.  She uses apps.  That’s what most people do.

Apple has dared to ask “can we remove file access entirely” from the user experience.  There are some cooler heads on the Internet that notice these are interesting ideas, and they may be fruitful.  Perhaps we should give them a chance.  The answer will likely be “not entirely”, but it can be different, better for 99% of users.

Kudos, AppleInsider for exploring these concepts in a non-mellowdramatic way.

A better camera: A 3 megapixel to 5 upgraded seems a minimal upgrade that should be expected. If it does include a better camera, it should also provide better programatic access to it. Allowing apps that use it to throttle the quality, especially those that use video, particularly streaming video. If you could stream low-res and save high-res at the same time, that would be ideal. It’s likely that cameras will appear in future iPod Touches as well, perhaps lower end versions.

Bigger and/or Better screen: The two aren’t the same thing obviously. Apple has been resisting the resolution “upgrade” because the one-size-fits-all has served their developers, and therefore their app breadth, well. Other platforms are already stratifying, and it’s not ideal. They will definitely need to provide the simulator support months in advance of hardwired availability, so that developers can confirm their products. They should also provide a way to run lower/original resolution applications, or risk minimizing available applications.

More customization: With each major release of the iPhone OS there are minor customization increases. There will be minor changes on this version and Dashboard-style widgets, custom backgrounds, or any other “skinning”-type functionality is unlikely. And in my opinion, unneeded.

A faster processor: Each hardware upgrade has included a processor improvement. Apple has no need or desire to be the fastest possible processor.  More speed = more battery use.   Apple will continue to err on the batter life improvement side.

Voice recognition throughout: Apple aims at the larger, non-technical market, and I think voice recognition and in particular voice dictation is a bleeding edge technology. This is still not available broadly on computers and mobile CPUs can’t handle it. The Nexus One offloads, necessarily, processing onto servers.  This bandwidth increase would be undesirable, particularly to an AT&T already straining from the needs of the iPhone.

Multi-tasking: This is most yearned for feature that is the most unneeded. Apps can currently remember their states if they care about their users. Having Apple “sleep” an app also leaves an ambiguity of when the user really wants to quit the app. There are definitely some functionalities Apple should open up to developers that happen to be background ones. (Audio Streaming a la NPR app – The stream should be on par with the Apple Music app.)

Greater Durability: I disagree with Dwight, iPhones are strong enough. Their screens are considerably larger than most which naturally makes them more vulnerable. And insurance is usually available for those unable to handle the iPhone safely.

Thinner and lighter: a competing design variable to Greater Durability.

Relaxed App Approvals: Apple did recently “stream line” its app approval process and items are getting through the pipeline much faster this month than two months ago.  A few more months are needed to see if this change is everything is needed.  This general heading in Dwight’s list is there only for a specific argument: Google Voice.   I would love to have that app, but any arguments are hard to make for lack of real information on why it hasn’t been green lighted.  Lots of rumors and speculation.

End Its AT&T Exclusivity: Apple chose AT&T on technological reasons. There are two (different, and not quite equal) 3G technologies. Apple chose the one that can provide more technically and the one that blankets Europe and Japan. There were also technical modifications made to AT&Ts infrastructure to allow the “audio voice mail” that would need to be made by other carriers. Cingular has the same type of network; Verizon would require the manufacture of a different type of phone. I don’t think the growth spurred by non-exclusivity would be large enough to bother production.

Error launching remote program: security policy error.

The app would terminate, the debugger was running but not attached to any process.  The fix that finally resolved it was going to Settings > General > Profiles on the device and removing all of the expired Profiles in there.  (Which were not related to the app in question.)

As you can tell, I was quite amused.

The Lede on this story sells the Gold Rush, no doubt leading young men West to dig in the dirt.

This article does point out the other side of the story briefly:

But the chances of hitting the iPhone jackpot keep getting slimmer: the Apple store is already crowded with look-alike games and kitschy applications, and fresh inventory keeps arriving daily.

But they quickly return and glorify the Get Ri¢h Story.  They return to 6-figure pronouncements and phrases like “minimal skill” and “only 7 days”.  It sounds like late-night hucksterism.

There are currently about 2000 apps released in the store per month.  Less than 1 a month is a get-rich-quick winner.  And those are usually gimmicks and one-offs.

There is a middle ground.  A reasonable expectations and reasonable skills balance.  But you won’t likely hear that story in the press.

I also wouldn’t be surprised if there were some big boys that back out of the arena in a year or two because of the dilution of perceived value.  They spend big bucks on game development and need to reap it back.

Of course, evolution in the hardware available is going to continue to change the landscape.

A friend of mine commented that her iPhone Internet is faster than her work computer’s Internet.

It’s bothered me for some time that the assumption is that companies can spy into your business as much as they want because “they provide” the equipment. Are you going to listen to my phone call to my doctor as well? Unfortunately, too often, the answer (given seriously) is “yes”.

“We have no respect for you. You are meat. Here’s your minimum + $x.” It seems odd on the surface, but obvious once introspected. The more people pay you, the more they don’t intrude on you. This has always been the case for me, and I’ve worked a wide variety of jobs.

Apple hinted in the comment section after their iPhone 3.0 announcement that they were exploring options for tethering your phone to your (laptop) computer. Your phone in your pocket. Your computer on the table/desk. The computer using the phone’s 3G Internet access.

That’s cool (and already available on some phones) and the pipe will only get larger in the future. You could easily tether your work computer to your phone to get better throughput, or to email your lawyer about your divorce, your doctor about your herpes, or sweet naughties to your spouse deployed overseas. And get back to work all the faster. And not fear for your privacy.

Of course, soon enough your phone will be as powerful as your computer.  But forcing employees to have separate avenues of communication is inefficient.  If you afforded them privacy in the first place it wouldn’t require it.  Providing them with sufficient Internet access speeds is another issue altogether.  (Time to dump the ISDN?!)

Of course companies are going to whine about corporate espionage, and to them I say: know your employees, manage them well, pay them well, keep them informed, and treat them like humans. That will avoid most of your problems.

Do you remember when Palm announced their upcoming Pre?  It was like a hullaballooed product release at CES.  It was so patently obvious (to anyone familiar with the technologies) that their wasn’t a lot of there there.

There was so much overreaching of claims by one major investor (trying to stoke more investment?) that it required an official SEC filing of facts. (source: AppleInsider – in sore need of copy editing, but an excellent article).  They now even claim it won’t be a direct competitor to the iPhone.  So, not good for Internet or games?

Indeed, AppleInsider contends that Palm is precariously positioned, and I wholeheartedly agree.  I think they will need a drastic influx of capital to finish and maintain development of the vapor platform they presented the world.  And this isn’t the most ideal economic environment for that to happen.

You can get the code at it’s google source site. There’s not too much documentation available, but it seems simple enough (as any SQLite wrapper should aim to be). There is a ReadMe.txt with a brief introduction, and some sample code (which I haven’t yet looked at).

I went about including it a different way than the “drop the zip file in” method it suggests. My project is in SVN and I’m using Versions, so I just added an svn:extern statement and now have a subdirectory with the source in it.

In Xcode I created a new group, then edited it’s information to point to the subdirectory naturally, then added all the files in there to the group. Then right-click on frameworks, add existing framework, and dig through the /Developer/Platforms et al. until you get to the sqlite dynamic library to link against.

It built and compiled fine for me. Now off to put it through its paces.

The article’s lede includes self promotion, and questionable attribution.

Last month, I posted regarding netbook rumors that were swirling in anticipation of the Macworld Expo. In my write-up, I suggested that in many ways, the iPhone and iPod touch already were Apple’s netbooks. -Ars Technica

The concept of the iPhone being a netbook offering from apple was first suggested half-jokingly on an Apple financial teleconference last fall. For Erica to suggest she has come up with some new analysis of the market by suggesting exactly what someone else has already said is either humorous or sad, I’m not sure which.