rock and scroll

iPad typing tip

Save time and organize your thoughts better with this simple tip.

I admit I didn't know you could do this for a long time.  Some users have told me this makes writing in Chapters a dream.  Hopefully this helps you too.

Using a static library in Xcode 4

Today I'd like to share some information on a topic that is dear to me: building static libraries with your Xcode projects.

I launched into testing something today and ran into issues I hadn't encountered under Xcode 3.  In the course of searching for the one right way to add static libraries to my project I found many forum and blog posts, all a little different from one another (and most from earlier this year).

Here are the steps for setting up my test project.

Set up your Workspace

First I created a static library project using Xcode's static library template (File...New...New Project...)

Next I created a workspace using Xcode (File...New...New Workspace). This is the preferred way of grouping related projects, and in this case I want to group my static library project with the project that relies on it.

Note that existing projects can be converted into workspaces (File...Save As Workspace...).

I created a new project called SimpleSearchDemo within the workspace. I then control-clicked under that project in the navigator to add my existing SimpleSearch static library .xcodeproj file.

A note: I repeatedly tried adding my static library project to this workspace but it kept appearing without the disclosure arrow.  After an hour or two I had a headache and restarted Xcode and tried again. It worked as expected. I still think about those hours sometimes. Collateral damage.

Edit your static library build settings

Next I selected the static library project to edit its build settings. I set it up to skip install and made sure the Copy Headers build phase included the headers. In particular, I added the public-facing header to the Public section.

Configure the project that uses the library

Once the static library was set up, it was time to configure the client project.

Link the static library with the project target; it should appear under 'Workspace' libraries.

Adjust the build settings so that the User Header Search Paths include the directory where the static library's headers are copied. I used the BUILT_PRODUCTS_DIR after reading this post. Both projects belong to the same Workspace, and thus share a common build directory.  Enable recursive searching of the user header search paths, and enable Always Search User Paths.

Finally, ensure the static library is built for archiving.

One other thing. I had issues with code completion working. I dragged the "public" header from the static library into the client project, and unchecked the 'Add to targets' checkbox.  Autocompletion started working (the header is right there, after all), but this seems unnecessary - let me know how you got around it.  Any other improvements are welcome.

Thanks.

Michelle and I quit our jobs (for the second time) more than two years ago. We moved from Atlanta to a smaller town and she started medical school. She wanted me to do something different and not rush into a job search.  I started working on things I found interesting and thought others might like.  I had invested in a MacBook and an iPod touch six months prior and was enjoying learning the iPhone SDK.  I even had a few customers on the then-new App Store.  I didn't know if I could make it last but it felt right to do what I loved.

These years have been very enjoyable for me.  I was surprised at just how sad I felt after reading the news.

 

The following is a nice tribute from the developers at Panic:

Screenshot from Panic.com

App copycats

I was browsing around the App Store tonight and noticed an app that
looks extremely similar to one I created last year. Have a look.

Above is a screenshot from MakeChange, an app I designed.

 

and here's Coin Math.

 

Not illegal, perhaps even natural,  but I don't really like seeing this.

 

The waiting is the hardest part

It looks like there's an issue with the latest update to Chapters. I
found out about it within hours of the update's release and had a fix
in Apple's approval queue shortly after. Based on what I've heard via
email, it's affecting roughly a third of you, most running
iOS 3.2.2.

The mistake is a one-liner. It didn't present a problem on my test
devices nor did it affect my beta testers. The Clang static analyzer
(set to analyze on every compile) didn't catch it either, though it's
caught similar issues in previous development cycles.

After submitting the update I wrote to Apple to request an expedited
review for the fix. I noticed the status of the app changed from "Waiting for
Review" to "In Review" days before it normally would have. I was
hopeful.

Unfortunately, it's simply been "In Review" since that time.

In the meantime, the app's ranking has fallen and some people are
understandably upset. One-star reviews are popping up. I still hear
from plenty of people that aren't having any problems but there are
those that are running into the issue. In many cases, the only reason
to leave a review is to say you're upset.

Some are urging me to fix this immediately and it's sometimes hard to
explain that this is as fast as I can go.

It's painful. While bugs are common in software development, they're
much easier to deal with then you're in complete control of the
release process. You can send someone a new executable. You can push
a new version to your production server and tell your customers to
click Refresh. Fixed.

But with this. We just. Have. To. Wait.

My least favorite part of the App Store, though it's been an amazingly
positive experience overall.

Chronicle for iPad - Top 10 apps

I check App Store rankings far less than I used to, but it was nice to
find Chronicle for iPad in the Top 10 Paid Apps list today. In recent
weeks many household names have been showing up in the store. It's
neat to be up there with Oprah, The Food Network, Martha Stewart, and
Esquire!

Thanks for your help.

Chapters for iPad: The Reviews

I released Chapters for iPad two months ago.  Since then I've sold thousands of copies, heard from hundreds of customers around the world, and released four app updates.

When Chapters debuted, it quickly appeared in the New and Noteworthy section.  Once it was bumped from that category it went straight into What's Hot, where it remained for a few weeks.  If it ever makes into Staff Favorites it'll have been featured in all three front-page categories. 

I was somewhat giddy seeing the app rank next to (or above) the always-in-the-news titles like Plants vs. Zombies, Words with Friends, and Apple's own Pages.

It's now out on its own, so to speak.  Despite a massive influx of new iPad apps every week, people are still finding it and filling it with the things that are important to them.

My journal is that of me which would else spill over and run to waste. - Thoreau

For me, the app has become something like a traveling gnome (less Travelocity and more Amelie).  I've heard from people documenting their vacations across the US, on a train in Australia, various parts of Europe, and more.  The Dropbox support lets them back up their photos and writing without needing to sync with iTunes.  

Others are busy using it at work to record meeting highlights and progress on projects.  Some people use it as a simple, searchable CRM tool.  Being able to type bullet-point lists and have a word count feature have been popular.

I've heard from people that use the app to take notes in college. I've also heard from two people in their seventies using the app to keep a journal.  Maybe the iPad is magical, after all.

I really like waking up to a full inbox (but not too full; I don't want to be one of those people that has to think about Inbox Zero).  Thankfully, there have been very few issues, so most of the email is suggestions and compliments.  I respond to every message.

I'm happy some people buy the app, make suggestions, and stick around to see their ideas come to life in an app update.

There's more to come.

 

A few reviews of the app since release

Four Writing Apps for the iPad

Tales of Joe and Jane

TUAW's Daily App: Chapters

Chapters for the iPad at Macgasm

iPad Application Reviews

GizmoFusion

TapScape

What's coming in Chapters 1.0.3

I just finished testing the latest release build of Chapters.  

It'll be available in the App Store as soon as Apple takes a look at it.  The format I'll use to describe a few of the new features implies one I'm omitting ;)

• You can pick a font for your notebook cover.  
• You can access a list of your notebooks and skip to them easily
• You can order your notebooks by date last accessed, keeping your most-used notebooks within reach
• You can optionally enable a word count display while composing new entries
• Easy tabbing while composing

This release comes close on the heels of 1.0.2, which added, among other things, the ability to create backup files.  If you ever lose your writing you can copy a backup file onto your iPad and restore everything.  Your photos will reappear too, right where you last left them.

If you have Chronicle for iPhone, these same backup files are compatible with both Chronicle for iPad and Chapters.  You can move entries back and forth between your devices as necessary.

Timing and the App Store review process

With web-based applications, you can move fast and break stuff. Every
user gets the fix you make immediately.

The App Store is a lot more like the desktop software market of the
90's. One problem is that most of the people using the App Store grew
up with the web and naturally expect quick fixes to any problems they
encounter.

A couple days ago I submitted an update for Chronicle on the iPhone.
I was doing some additional testing on its 3rd day in review and
noticed a problem. The release version of the build would only run on
newer hardware (iPhone 3GS and 3rd gen iPod touch or newer).

As luck would have it, the app was approved before I could remove it.
Normally approvals take about a week, so this would normally be a
great surprise!

I submitted a fix within 10 minutes and hoped for the same speedy
review process. Unfortunately, it's been more than 3 days and a few
one-star reviews have already been coming in, despite the warnings in
the app description and what's new field. Long-time users have been
understanding, but others have accused me of letting things stay
broken for *days*, with no regard for their time or money.

It's crucial to test and retest, and properly evaluate your 3rd party
library build settings! I screwed up.

Thanks for your patience.

The most frustrating app reviews

Reviews at the App Store are supposed to provide some measure of social proof.  If reviews are fairly positive, chances are it's safe to spend your money.  The assumption is that the reviewers share your concerns and sensibilities.

Unfortunately, some people are so far out on the curve you should ignore them.  

A single bad review among a dozen positive ones stings me more than it should.  Worse, it also influences purchasing decisions.  People are naturally conservative with their money, so if there's a shred of doubt they may move on and avoid the risk.

Most people know when a review is bullshit, but it's not always obvious.

Here are a couple things that frustrate app developers and have the greatest chance to impact sales negatively.

The ones that ambiguously criticize standard UI elements

If someone is using an iOS device for the first time, they may not be familiar with the standard controls, gestures, and dialogs.

Someone wrote a review about one of my apps and expressed extreme frustration with one of my screens.  I realized they were talking about the standard MFMailComposeViewController (the screen you see when you want to send an email from an app) and had mistaken it for the main screen of my app.  We resolved the misunderstanding via email, but he never changed his review.

The problem is that it's not entirely clear what screen he's talking about in the review.  A casual window shopper simply sees that there's a seriously does-not-work-as-expected screen in this app, and they move on.

The ones that seem desperate for help, but never seek it

Sometimes, among many positive reviews, someone will barge in with a shocking tale of woe and confusion.  They lament the loss of their money and make it seem like they've tried everything.

This is particularly frustrating when, as the developer, you know the person hasn't read the app description, hasn't used the in-app help, and hasn't contacted you.

If you really want help, want a solution, and care about your money as much as you purport to, contact the developer.  I once spent 4 hours helping someone recover some data after an iOS update and sync wiped out all their apps.  I'll do what I can for anyone having trouble.

I provide in-app contact methods, as well as the support links on iTunes.

These kinds of reviews are confusing because there are others that follow the same pattern and are genuine accounts of a crappy experience.  Thankfully, other users will often correct a reviewer in their own reviews, but this doesn't happen enough to negate the problem.

The App Store has some amazing values

Think of all the great pieces of software you can buy for less than the cost of a drink at a restaurant.  Even more amazing, if the waiter at the restaurant keeps your glass topped off you're expected to spend more and leave a big tip!  

Horrifically, the drink is automatically uninstalled the next time you visit the toilet.

With apps, you get updates for free and most apps are niche enough to afford you a direct line to the developer(s).  You can send suggestions and influence the app's development.

Real estate timeshares might be a questionable investment, but investing in a developer for a couple dollars is a great idea.

Developers want to talk to you

I hear from a lot of customers via email.  I love reading and responding.

As for the App Store, hopefully developers will eventually be able to respond to individual reviews.  This will help correct some of the information asymmetry present in these situations.

 

 

Apple Staff Favorites and App Store Sales

Yesterday Touchcards 2 was featured in the App Store as a Staff Favorite.  Throughout the day it rose in ranking on the charts, and this morning, as you can see above, it's at #47.  Prior to being featured, it had reached #90 or so.  I knew from articles about what getting featured does to sales to expect a bump, and I got one.  But one thing to note about the Staff Favorites section is that it's not actually available from the App Store app on the iPhone itself.  You apparently need to be using iTunes on your computer to see it.  This makes the sales jump a lot less dramatic than those featured in the AppAdvice post.

The staff at the App Store see thousands of new apps each week in a store with over 140,000 apps.  To be hand picked means a lot.  I also thank the customers that take the time to share their "success stories" and creative uses of the app with me.

If you've downloaded Touchcards 2, you can expect an update shortly (it's in the approval queue) to give you better font sizing support.  I have a few other things planned, too.  It's great to have new users more than anything else!