Using the Facebook app requests dialog means I can send an invite to a user. Usually this invite will appear in their notifications menu at the top of their Facebook page. And I will see:
“Mike Hogan sent you a request in FooApp”
Which is not at all compelling to a user. If they click on this notification, it takes them to the front page of FooApp, without much context of what the invite is. I’m experiencing about 85% tail-off of my App Requests done this way. Understandably.
Users do get a chance to see more detail of the request if they click to view all their App Requests, but who does that?
I have received requests from other apps that appear in my top Notifications menu, along with a red diamond, that when clicked on, take me to the App Requests page, instead of directly to the app. This allows me see more context of the request, instead of being hurled in ignorance at the app’s front page 😉 This might work better, but I have no idea how to make that happen – how to make clicking on an app request in the notifications go the the App Requests page instead of to FooApp.
So I am wondering how people get App Requests to work for them?
Any and all ideas much appreciated!
Thanks,
Mike
From this page: https://developers.facebook.com/docs/requests/
“Requests that are Invites (the recipient user has not installed the app) do not display the message parameter and are categorized differently in the Apps and Games Dashboard.”.
So people who have not installed your app get a less inviting message. The best option in this case, as far as I can see, is to do what jBit recommended and display as much context as you can when a user lands on your app with a request_id in the url.
For users who have installed the app, they get to see the more detailed message.