A couple of questions on the new search screen: Does the search screen search and return content in the app, or does it just search the text in the screen nickname? I put the screen in a new app, downloaded the source code to test it - - it seems only to search the name of and not the content of my HTML screens. Unless the search term is in the screen name, no result. The hide from search is off - so the screen should be included. For my apps, the ability to search content would be very helpful - am I missing something? Second, how does one add a search screen without confusing existing users? Since the source code must downloaded, I assume that an update must be submitted to the app store. Yet the search screen will appear once it is added, but will be not found. I'm trying to figure the best way to do this - maybe recompile the code, submit it to Apple and not actually change the screen until the new version is approved? Thanks much.

Same question here. And David, for Webby Awards 2012, does 'inbound links to buzztouch.com' means link to buzztouch.com from our own web sites? If so, I have done it already, anything for you after all the things you've done for us :)

@DPinoh The search menu works like a simple Apple tableview. It will only search the titles of pages, and only in a sequence. If you want to find Russian River, you must search Russian, not River. This search function works perfectly for my app, since the search is for locations, and not internal content. Is there any way you can strategically name your page nicknames so that the search becomes intuitive? I could be mistaken, but you're the one with S+S rulebook? If you name a page about car searches - Car Search - then users will figure it out, or at least we hope so :P. On your second note, I'm wondering the same thing. I made another post about it before having read yours thoroughly.

Ah, I was afraid of that. . .that search function would be of very limited utility to my users. You are correct regarding the nature of my app - but most users of legal apps (I have an evidence app too) are used to a content or Boolean search. Ah well. Regarding the update, I love the ability to add, edit and delete content on the fly - but I haven't figured out the update issue. If I resubmit the binary, I suspect Apple will reject it saying, Not enough change. If I add the search screen (especially as the menu screen), it will essentially disable the app until Apple approves it - right?

Apple shouldn't reject it, I've submitted updates with less. The only noticeable difference should be a nonfunctional search screen. Otherwise, your app will continue the work as it did until the update is approved.

This is for sure our first-run for content search. Today, like you're realizing, it's only searching the Navigation Bar title of each screen. This has lots of utility for some, zero for others. There are TONS of things to consider when searching actual content. Consider what the engineering involved in searching content that comes from a URL, content that searches text inside HTML, etc. Tough problem too solve. However... we have considered a few ways to get around this and add at least some aditional search functions as we continue to evolve. a) We could introduce a dynamic menu option. This would allow app owners to setup a search screen that posts (http POST to a backend) a search variable. The backend would then use that search term to identify content (from a database, file system, other source) to use to create a dynamic menu of options. Hard to understand for some, easy for others. Dynamic menu-screens are coming and for sure will include an option to add a search-box to the header so the app owner can customize the menu from their backend content. b) Searching today is simple, 'find content that starts with' the entered character. This could easily be changed to use 'contains' instead of 'starts with'. In fact, this should probably be an option in the control panel. Changing this on your end will take :90 seconds. BT_Screens > BT_screen_menuSearch.m, around line 476. Look for... if(r.location == 0){ [self.filteredMenuItems addObject:thisItem]; } and get rid of the if(r.location == 0) condition. Just comment this out like: //if(r.location == 0){ [self.filteredMenuItems addObject:thisItem]; //}

That simple! Great, now I won't have to worry about all those Upper, Lower, North, South locations. :)

I just got around to adding a search screen in my app and am amazed I hadn't done it before. I am having the same problem as some others in that I can only search the beginning of the navigation bar titles. So, using examples from before, if I have North Philly and South Philly, I can't search for Philly just north or south. Dave, I followed the advice you gave above and changed the BT_screen_menuSearch.m file to the following: //if(r.location == 0){ [self.filteredMenuItems addObject:thisItem]; //} however when I reinstalled my app on my phone I still can't search for Philadelphia. Am I missing something? I know it's christmas eve so I don't expect responses right away :) Happy holidays!! josh

ignore my post, I'm an idiot. There is a line with if(r.location above what dave mentioned and that's where I put the first set of hashmarks. Now it works fine. Thanks as usual... josh