Dr. Touch is waiting to see if he can fly to the US, there’s a volcano in the way. At the same time Apple unleashes hell in their developer agreement, delay of the international iPad release and lightning-fast new laptops. Today Mike Vallez is my special guest, we’ll talk about iPhone app marketing and his new eBook Secrets to Effective iPhone App Marketing.
If you purchase a component from the Dr. Touch’s Parts Store you will receive a quick start guide which includes the access details to the Subversion repository that keeps my code. The address of the repository uses HTTPS protocol, which confuses some people into thinking that they could use a browser to download the files.
That’s why I made this video showing how to properly set up your Xcode to get the source for any part onto your harddisk.
The advantage of following this guide is that you end up with a “working copy” of the contents of the repository. That means that you can simply pick “SCM – Update Entire Project” and you get your copy updated to the latest version.
There are generally several methods how you could add external code to your own project, besides of simply copying it. The problem with just copying is that it’s quite hard to keep all the individual copies of a framework updated in all of your projects.
In my case I am continuing development on most of my components if I add them to one of my own apps, but I don’t want to have to make all additions that I put into the new project into the component project a second time. Development is boring if you have to repeat steps. Surely there has to be a method to have the updates stream back from the app project to the component project.
In fact, there is. The technique to use is called …
Previously I explained how to make a static library that simultaneously supports multiple different CPUs. At that time I was ignorant to the reason why there are no means to make iPhone frameworks. But I did not give up searching, especially since apparently a few individuals seemed to have pulled it off without properly documenting their method for others to duplicate.
The only guide I found is from two years ago, but I was able to verify that it works and so I will document it in an article so that many more people can use this great mechanism. But first, let’s briefly explore what it really IS that Apple does not want us to do. The generic statement that you can read on thousands of pages is “Apple does not want you to make iPhone frameworks”.
But is that really so? It turns out, this statement is not entirely accurate or rather specific enough to be the truth.
Seems there is an ever-growing community about my little tool GeoCorder which I originally made to get GPS data for testing. It evolved into a light-weight utility many people use for geotagging DSLR photos.
A user informed me that I messed up with the 1.0.4 version of the free variant. Seems both versions got out of sync. The only difference should be that the regular version costs $1 and the free versions has a banner ad. So I went in and fixed a couple of things.
Fixed some memory leaks
Updated AdMob framework in free version
replaced a deprecated function
fixed the free/paid inconsistency
Now all the new features from 1.0.4 are also in the free version as it was intended.
UPDATE April 16th: I had to self-reject my binary because it appears that there was a bug in the ZIP routine. I also added an extra switch to not record events when you are not moving. I removed the 1 Meter setting for the distance Filter because it looks like CLLocationManager ignores that. This gets replaced by the switch.
UPDATE April 17th: Self-Rejected another time. User asked me to change the XML Version to 1.0 for compatibility.
For some reason Apple reserves the ability to create iPhone frameworks for their own use. They are a very useful ability to have because they package headers together with a universal binary. „Universal“ meaning that you get binary code for multiple platforms rolled into a single file. Frameworks are also dynamically loaded which means that less binary code fills up your memory as only stuff is put there that is actually needed.
But alas, no frameworks for us.
Until now I am selling my components in the Dr. Touch’s Parts Store as source code which at the same time means that I could not provide demonstration versions to try out in your own code. If you have the code, what incentive is there to pay the price?
It has been suggested to me by several people independently to make a static library to solve this problem. Could be time- or otherwise limited, but then people could try the parts out and see how well they fit with their own work.
Also next to still offering access to my repositories at full price, I could be selling indidual versions without right to upgrade to get started at a substantial discount. Later if you find that the component really IS worth what I am asking for, you could upgrade to the lifetime upgrade plan via the SVN repo.
Another reason to figure out this Static Library Magic is so that I can bundle my own utility classes that I keep adding to and improving in a central place. This gives me the choice of adding an external SVN reference or to simply copy the static library into my new projects.
In this article I am describing how to create a universal static library for both Intel and Arm architectures, how to glue them together into a single file and how to add it to a new demo project.
I’ve been approached by several parties asking for a component to capture live video. I did my homework but had to find that without access to a hardware-based video encoder it is not possible to get real time frame rates on iPhones.
Interviewing the maker of the ShowTime Video Recorder app for iPhone 2G and 3G enlightened me a bit as to what tricks they used to pull off their app. They use AVI containers for JPEG frames and PCM audio. Other people seem to have a bit of success with compiling FFMPEG on the iPhone. But generally MPEG4 does not use less CPU power than encoding JPEGs, it uses MORE, causing even worse frame rates for live video.
And that’s ignoring the licensing problems you get when selling an app that has a h.264 encoder. A double-whammy in non-feasability for FFMPEG, all the more reason to find out the truth of the matter.
So we set out to build DTVideoEncoder to see for ourselves what kind of performance we can get. Unfortunately it turns out that even on a 3GS we are getting a maximum frame rate of 5 frames per second when encoding live screenshots. Polar Bear Farm hinted that they are only able to get their performance (of around 6 fps) because of heavy assembly-optimizing the JPEG compression library . But they communicated a disinterest in licensing it for us to put into a sellable component.
So we were stuck. Until actually somebody told us that instead of live video encoding he just wanted to add JPEG files to an AVI container plus audio. Because the JPEG files where already compressed he would not face the bottleneck of JPEG compression. Suddenly this specific use case reinvigorated the project.
Kris Harris – maker of the 8 Track Mind iPhone game – went back into the depths of the AVI documentation and polished up DTVideoEncoder to be usable for offline encoding and added the requested capability of adding an existing PCM audio file as soundtrack. Kris is a great developer and his code is awesome, I’m glad to have him on my Dr. Touch Core Team.
Here’s a demonstration of the Demo app that you get with the component.
DTVideoEncoder does not have any external dependencies. Because the external JPEG compression library did not yield any performance improvement over what’s built into the SDK we chose to go with the on-board method.
Hours and hours worth of research and coding went into in this simple to use component to warrant a price tag of several hundred dollars. But because of the limited utility we we set the price to the lower end of the spectrum, at 250 Euros. It might enable one or more interesting uses of offline-video on iPhone or iPad.
A friend/coachee of mine teased me with a picture showing him in loving embrace with this new iPad. I will be a couple more weeks until I can actually purchase one for myself. So I figured, I would want to give several developers that read my tweets and blog articles a change to show off their new iDevice as well.
We Europeans have a bit more waiting time, especially guys from smaller countries who want the iPad just the same, but have to bear Apple’s worldwide rationing of iPads due to initial touch panel shortage.
Stefan Sorin Nicolin, from Spielhaus FTW, illustrates for us the general mood amongst non-US-would-like-to-be-iPad-developers. He still has to imagine their famous Today ToDo app running on the shiny thing.
But for some the motto of this article is the opposite …
Smile! You’re Actually Holding an iPad!*
* …and are ENVIED by most of the rest of the world
Having some contact with developers around the globe allows me (and by extension YOU, my dear reader) a glimpse of what kind of apps are going to become available with the iPad on April 3rd. More importantly, we can ask those busy developers – who struggled to be first in the launch line-up – what they thought were the difficult steps in designing and building iPad apps.
Being the good soldiers that we are, we let them have the glory from being first while being able to learn from the problems that the one or other Apple mine would have caused them. Maybe this way we can save ourselves some grief and frustration if we can avoid their mistakes from the get go.
So here are 5 of the first iPad apps and what their developers learned from making them.
When you look at the Contacts.app you see that Apple somehow manages to change the size of cells in UITableViews of grouped styling.
If you search around on the internet most of the solutions getting such a look revolve around making your own UIView and adding this as headerView to a section. Now if you want the cell on the right side to still behave like a cell is expected to behave then you have lots of work ahead of you. So I consulted the twitterverse and here props have to go to Jason Terhorst who hit the bull’s eye:
If I recall correctly from Apple’s example code, they just clear the background, and redraw that rounded rect at new size. It’s been a while since I did this, but I think I swapped in my own custom backgroundView.
I researched and experimented for a day to get it perfect. What follows is a description of how to pull off this magic trick, so you can do so too. The end result will look like this: