So let’s say you have a client who wants to post to Facebook from their iPhone application. You could probably find on your own the official SDK here,
but here’s a few additional resources to help you along:
RaddOnline: Using Facebook Connect for iPhone tutorial is a nice introduction if you’re completely new to this Facebook app creation thing. (Or to Facebook, period, like those of us who actually do useful things with our time…)
Mobile Orchard: Marketing In Code, Part 1 is worth a gander to judge its claims about Facebook being an effective marketing method –
One status update or feed story to 13 average Facebook users users generates the same exposure as spending the entire post-commission revenue for one app priced at the average of the top-100 paid apps.
– but Part 2: Setting A User’s Status In Facebook From An iPhone App is where the step by step instructions are, along with a set of helper classes that can be found on github.
Posting Links to Facebook Profile from iPhone Code shows how to elegantly — excessively elegantly, even the author suspects:
I guess that’s precisely the thing: there is just so much code there for such a little thing! Two levels of delegation, six separate files, and so on. It’s hard to escape the feeling that we let some unnecessary architecture astronautism enter our heads when doing this.
extend the MobileOrchard helper classes from immediately above to deal with the Links.post Facebook API.
and if the above doesn’t sort you all out and you need to ask a question, this is probably the right place:
Facebook Developers Forum >> Mobile and Handheld
So there you go: all you need to get your Facebook integration nice and smooooooth, we trust!
Never been called an architecture astronaut before. Hrmph.
Okay, so why 6 files? Let me start here:
Divide by 2 for header/implementations. That’s 3, not 6.
There are two tasks: (1) establishing permissions and (2) doing actual work.
Both require using the FB API via the FBRequest message. Any FBRequest call results in a callback to request:didLoad — make two requests in the same class (e.g., get permissions, post a status update) and the same method is called back twice. So now you have to keep state somewhere. I wrote to Joe about this and he suggested I either use an instance variable or a tag and put an “if” into request:didLoad. Blech. So, one class for each task.
I anticipate/anticipated links and photos to the lib myself. Wanted to let people just use a single class to do all their work, and to simplify things by using properties (e.g., fbHelper.status = @”irritated at being called an architecture astronaut”). So you need a that third pair of files. That accounts for all the files.
Now, delegates:
First of all, everything’s optional from the end user perspective. But, if you want to know whether something happened successfully then you need them. Those things that you’re interested in happen in those aforementioned files and get sent back to the main helper class that dutifully just passes them on.
[b]digital cameras[/b]
This is a blog about [url=http://undergroundphotographer.com]digital cameras[/url], images etc.
http://undergroundphotographer.com
Just wanted to say hello all. This is my first post.
I would like to learn alot here.
Hello.
My computer worked slowly, too much mistakes and buggs. Help me, please to fix errors on my PC.
My operation system is Windows XP.
With best regards,
textAlutH
Hi Ya’ll!
I’m new to this forum and just had the urge to introduce myself and say “wuzup”.
Finally a solid website with colors that I can look at – which truly is a rare find!
I’m here to make friends + participate. How can I best contribute?
Laters Ya’ll!!!
Hello,
My computer worked slowly, too much mistakes and buggs. Please, help me to fix errors on my computer.
My operation system is Win Vista.
Thanks,
Prayenofleern