vlbeta

Yeah, that type of job search would be hugely helpful. Some of the other questions that come to mind are:

Q. I'd like to bike to work - within 10 minutes - within 20 minutes - i don't bike to work

Q. I need health insurance - the full package - at least medical - not important

Q. I'd like catered meals - every day - occasionally - not important

We just built out a new job search as well and have been thinking about this quite a bit - https://jobfusion.co

Looks like there are about 43 software developer jobs in Grand Rapids, MI. Enter a programming language or skill in the search to hone in on the results.

https://jobfusion.co/grand-rapids-mi/software-developer

Are you concerned at all about copyright issues, scraping content off sites and reposting it as your own?

The real problem lays in the default trained behavior of the user - leave a review if _anything_.

Both app developers and Apple have wrongly been pushing users to voice opinions publicly in app reviews, leaving app developers exposed with no way to communicate with those users.

The solution is to start pushing users to communicate their suggestions and issues privately, in the app, where you can better manage conversations, keep users engaged, and build relationships that can turn upset users into long-term evangelists.

The real problem lays in the default trained behavior of the user - leave a review if _anything_.

Both app developers and Apple have wrongly been pushing users to voice opinions publicly in app reviews, leaving app developers exposed with no way to communicate with those users.

The real solution is to start pushing users to communicate their suggestions and issues privately, in the app, where you can better manage conversations, keep users engaged, and establish relationships that can turn upset users into long-term evangelists.

1) Do not bury support or email buttons multiple taps deep. Surface a contact button so that it's easier for users to contact you.

2) Do not ask users to fill out more than a single field to send you their thoughts. Automatically capture user ID, device, platform, OS version, app version, etc. by passing a unique session or user ID.

3) Keep them in your app, engaged, and talking. Think of this more like "user relations", not "user support". You need them engaged and sharing their thoughts more than they need you and your app.

In terms of what can be done now for helping to avoid iOS 7 app reviews, here are a few suggestions:

1) Add an alert for iOS 7 users that your app is not yet compatible: http://mobile.tutsplus.com/tutorials/iphone/uialertview/

2) Here's an example:

[[UIAlertView alloc] initWithTitle:@"Unsupported iOS Version" message: @"This version of the app is untested on this version of iOS, please check for an update in the app store." delegate: self cancelButtonTitle:@"Skip" otherButtonTitles:@"App Store",nil];

2) If you have an email list of your users, send them an email with when they can expect the OS update. Users will expect a great, new experience with iOS 7 and will be deleting apps that don't meet their expectations. You can't expect users to keep using your app when there is so much new "eye candy" on the App Store.

P.S. Stuart from Appbot actually covered this with a scary screenshot of iOS7 reviews only one week into Beta1: http://stuartkhall.com/posts/stop-allowing-app-reviews-from-...

Another: http://textmessageapi.com

http://www.zeepmobile.com/ and http://www.textmarks.com/

Although I'm not sure if they support Brazilian carriers.

http://www.pennysms.com