iPad and NYT
The New York Times was a bullet point in the iPad introduction. The application they had already developed looked quite nice from a cursory glance, particularly with its lack of advertising. The Apple Gazette recently discussed the pricing conundrum they are having at NYT.
There have also been rumors that most of the Times’ content is going to go back behind the pay wall. Assuming that is the case, I think there’s an obvious strategy for moving forward with their iPad pricing.
Initial price: $10, and that covers 3 months of content. Get everyone hooked! After that start charging $10/month. Also, strategize how you might include minor and strategic advertising content into the app. Possibly set up a new pricing scheme for advert-less versions.
Also, make sure you build in a “you can’t buy next month’s content until you upgrade the app to the newest version available – it’s free”. This would enable you to enforce any new restrictions you add to the app and keep the majority of your customers on the same version.
Of course, I would prefer if it were free. But that’s not how businesses work. If they keep the entry cost low enough, it might be enough to get me back into the daily habit of reading the newspaper again.
Inconceivable: I Can’t ‘ls -l’ My iPhone
Vizzini (played by PC World): Inconceivable.
Inigo Montoya (played by Apple Insider): You keep using that word. I do not think it means, what you think it means.
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.
Protected: Xcode 3.2.2 beta Issue: Install on Device
Enter your password to view comments
iPhone 4.0 – What Will The New OS Bring?
Dwight Silverman recently provided a large number of “improvements” he feels are necessary for the next version of the iPhone. Here are my opinions on his thoughts:
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.
New Provisioning Profile Not Working: Fix
My Provisioning Profile for my iPhone app expired, so I renewed it, downloaded it. Added it into Xcode. Manually added it to ~/Library/Mobile Devices. It would build and install onto the device, but when launched via the debugger I received the following output:
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.)
Checkers FS5 Free Pulled From Store
After waiting for Checkers to be pushed into the store from the queue, and watching it’s soft launch this weekend, we noticed some anomalies in the ratings. We’ve come to have certain expectations of the ratings.
The Checkers FS5 Free was receiving an inordinate number of low ratings. No comments explaining or support emails about it. Unfortunately, this is typical of users. Only one of our team members has a 2.0 device we can use for testing. He launched it and immediately found the problem. A slight timing issue with some of Apple’s libraries causes the game to hang when you start to play it.
There are still quite a few 2.x iPod Touches, and they are particular in their game play. We had to make the decision on whether to pull it or not, it was touch, but that’s what we decided to do. The simple workaround should be back in the app store queue by the end of the day, but it may be a while before it sees the light of day in the app store.
We’re sorry for the delay, and in the mean time if you want our checkers you’ll have to pay for it.
Versions and svn merge
We had a project that included extern links to many subprojects. (They were subprojects because we use them across several projects.) The subjects had a iPhone 3.0 branch created for them, and developed against the new SDK. Out of laziness, we redirected the extern links to the 3.0 branch when it was desired.
In reality, we should have created a 2.x branch, and forced existing apps to change what they were looking at or use the new 3.0 code. But we didn’t.
Now, it was time to merge the 3.0 branch back into the trunk of our development. Version provides a realy nice GUI to most of your day-to-day svn needs. But a major merge is not an everyday need, and needs some human interaction. (Though I do think they could supply a “merge repository branch X into workarea branch Y, and let me handle it from there”.)
The first thing to do is change the external settings to where you want them to be pointing when you’re done, trunk in our case. You can do this from Versions in the externals part of the inspector. Then re synchronize the project. At this point it likely won’t build. We need to move the code from the branch repository into our trunk work area.
One trick before merging is determining at what point the branch split from the trunk or was last copied from the trunk. I have a work area with the entire subproject branching structure sync’ed to it and you can select each of the two and show their history, and compare the commits. The last common commit is what you are interested in. Mine was 158.
so, you’ve changed directory to the trunk work area, the money command is:
svn merge -r 158:HEAD <branch-workarea-path> --username <remoteuserid>
it will ask your password more than once, keep giving it,
it may ask you a merge question, i always postpone, it provides standard in-file diffs you need to handle,
Select: (p) postpone, (df) diff-full, (e) edit,
(h) help for more options: p
After handling the diffs, check it in.
G-phone
I still don’t have a cell phone, but I do have a new number. Google voice. You should be able to leave a message below. This crazy technology world!
Too Much iPhone?
I was video chatting with my co-worker in Virginia, fellow FlipSide5 jack-of-all-trades Mike, and he decided to show me his quite impressive collection of iPhone OS devices. Different hardware versions of iPhones and iPod Touches with different versions of the operating system on them. Useful for testing the various possible compatibility issues, but really useful for little else.
As you can tell, I was quite amused.
Flip MinoHD
Here’s some test video I shot with my new Flip MinoHD. It’s my nice bucolic back yard in the Houston Heights: three miles west of downtown Houston, one of the larger cities in the United States.
I did a slight amount of editing with iMovie (not iMovie HD – if anyone knows the difference could you tell me and let me know which one I should be using).
I used the image stabilization in iMovie. It seems like it gave it a little “shimmer” toward the end. The hand held was slightly more shaky looking that it ended up after the stabilization.
I exported it in “medium” size (3 of 5 in size, 6MB for 0:31), just because that seemed the most reasonable for a web test (it was still too big for WordPress media editor to want to upload). So, here it is…
(maybe i’ll learn how to embed video on my WordPress)
