-
Jesus Phone in hand
As I indicated in a previous post, I planned to get an iPhone 4. I pre-ordered it, but since I was late to the party, it wasn't going to arrive until July 15th or so. I had wanted it sooner as I was going on 2 trips before then; I don't travel all that much, so having it would have been convenient.
I tried Wal-Mart, but they didn't have any on launch day. So, on Thursday night, right before the Apple Store closed in Fashion Valley, I called and asked about stock. The guy I spoke to said that they should get more on Friday and people would be lining up before they opened at 8 am. So, I decided to give it a try on Friday. I arrived at around 8:05 am and got in line. The employees that came out indicated that they had stock, so I waited. I spent about an hour and 10 minutes in line and finally got in the store. It took about another 15-20 minutes to process my order and I was out the door with my phone.
So I bought into the hype and lined up for a phone; however, I didn't line up at 5 am like other people did. Apple constrains supply and I think fudges numbers to get on the news, which is what happened. If Apple had stock to sell me, why couldn't they ship me a phone and have it delivered the day after launch? I guess that wouldn't get them the free publicity.
Now that I have my phone in hand, I'm reasonably impressed with it. I'm less impressed with AT&T and their coverage, but we'll see how that goes. I did find what I consider to be a very annoying bug with the cellular radio in the phone; if you go out of coverage area for an extended period of time, the phone stops searching for a signal. I had to put it into airplane mode and then turn off airplane mode to get it to search again. I understand power conservation, but you'd think that it would simply try less often to get a signal. What is also strange is that I had coverage, went inside a building, completely lost coverage (the building was a wood framed building, I believe) and never got a signal back. Someone else next to me had a Palm Treo on AT&T and had 2 bars of coverage.
-
The future of TV
A few weeks before Google announced Google TV, I experienced the future of TV, at least as I see it. We normally record our programs with the EyeTV hooked to a Mac Mini. However, sometimes the EyeTV has a fit and we don't get everything recorded, but that's another story. Since our media center is a Mac Mini, I simply used screen sharing to access the Mac, used a web browser, went online to CBS's Web site (I think it was CBS), and played a show in HD. It streamed quite well on our TV and the commercials weren't all that annoying. The only problem, however, is that the Flash ads sometimes pop the viewer out of full screen and require me to use my laptop to put it back. If I wanted to watch TV without my laptop on my lap, this would be a problem.
We've now started to watch more shows this way and it is convenient. It allows us to watch shows that we haven't recorded; convenient during the summer when our standard shows aren't on.
My hope is that Google TV will build upon this concept and allow people to use a television remote to watch TV on the web without having to pay a ton of money for cable. We're a family that only subscribes to basic cable (it comes with HD for the broadcast channels as it is required by law), so the concept of Google TV could work for us if it let us watch shows that are already available online, free of charge.
-
A month of being self employed
I've now been self-employed for a month and things are going quite well. Right as I left my job, pieces fell into place which gave me steady contract work. My contract projects are going well with very little pressure (I don't consider a deadline a lot of pressure as I simply have to get the work done). Every morning when I start my day, I look at the phone on my desk expecting to see a missed call. It still hasn't happened; my work no longer consists of going from one emergency to the next.
The projects I'm working on are challenging in that I've taken over someone else's code, but I like challenges. At the moment, I'm mostly just doing bug fixes, but that's fine with me. I'm pretty much left alone; issues are assigned to me, I fix them. Everyone's happy.
My stress level has gone down significantly and I feel like I've gotten my life back. I'm still probably in the honeymoon phase (I know I've said that before) of self-employment, but I'm hopeful that this feeling will continue.
-
iPhone Developer Provisioning Portal Tips
Recently I've been put on 2 different iPhone development projects and on both projects, I'm responsible for doing the builds. Any developer that has dealt with the provisioning portal knows how confusing and how much of a pain it is to use. It looks to me like there is a bit of confusion over the portal, so here are some tips.
- There are 2 types of distribution mechanisms; one is through the AppStore and one is AdHoc distribution. So, they need to be differentiated in the project and on the portal to make it clear.
- In your project, I recommend creating 3 configurations; Debug, AdHoc, and AppStore. This makes it clear what you're doing.
- Only the Team Agent (the person that signed up for the developer account) can create the distribution mobile provisioning files (AppStore or AdHoc). So if you as the developer didn't set up the account, you either need to get the credentials of the person that signed up or bother that person when you need to add/remove devices for the AdHoc build.
- Name your provisioning profiles in the portal with AdHoc and AppStore (respectively) so you can easily select the right profile in Xcode. Naming one Distribution is not very helpful.
- Bundle the AdHoc mobile provisioning file with every build sent to testers; the file is small and then no one has to ask you for the file later.
- Save yourself some headaches and check the mobile provisioning files into source control.
- Export the private key and certificate used to create the distribution profiles as a .p12 file and check that into source control. Depending on how paranoid you are, you might also check in a file with the password for the .p12 file. The next developer that takes over your project will thank you for not making them jump through hoops.
While some of this may be obvious and I'm sure some people won't agree with what I say, I think that these tips really make it easier to manage iPhone development.