Experience.FellowshipOne.com

I was curious to see if anyone on 3cords also has an iPhone.

Read my blog about it.
http://tammanyweb.com/blog/tech-ology/2007/07/iphone-part-1.html 

Although Safari is NOT supported for Fellowship One, I am open to discussion / questions about use of the iPhone with Fellowship One (or just in general).

 

 

 

 

I love my iPhone, but working with F1 on it is a hassle.  I was wondering if making a site with the API would be worth it, but the API just doesn't do much but edit the individual's information.

There is a lot of opportunity of functionality for the iPhone - especially with 3rd party apps soon supported for the iPhone.

When you say working with F1 is a hassle on the iPhone, do you mean the mobile version of Fellowshipone, the portal or both?

fellowshipone.com

mobile.fellowshipone.com 

 

Jared 

 

---

Jared Farnum

I have an Iphone and the mobile version just started working for some of the drop downs, but not all of them.

As for fellowshipone.com, it seems to work just fine. I like it better than the mobile version.

Do you know of a way to change the default browser to Firefox instead of safari? 

Beky 

Becky,

At this time there is not a way (at least as Apple intends) to install Firefox on your iPhone. However Apple should be releasing a SDK (Software Development Kit) any day now. Steve Jobs had promised in February, however that has not occurred yet.

I would expect that there will be tons of applications released soon after the SDK is released, hopefully Firefox will be one of them.

 
 

---

Jared Farnum

I just got my iPhone and haven't tried using F1.  I had planned on writing a little web app using Data Exchange for searching for people but seeing there is a mobile version... (by the way you might want to advertise things like this ;)  I still may just for proof of concept though.

  

---

Mark Spidle - IT Director
Point of Grace Church
markspidle@pointofgrace.com
www.pointofgrace.com

I meant the full version of the F1 portal when I said it was a hassle.  I didn't realize there was a mobile.fellowshipone.com.  The mobile works great on the iPhone for what it does.

Any comments on this video?

http://www.apple.com/quicktime/qtv/iphoneroadmap/

 

Jared 

---

Jared Farnum

I'm thinking my new favorite platform.

I downloaded the software, but I haven't been productive with it yet.  I need a crash course in the Obj.-C programming language.

Also, with AIM for the iPhone, there will be no need for expensive text messaging bills, something I have been waiting for. 

Ditto to that; if the Exchange support in v.2 is as good as it looks to be, the iPhone has a good chance to become our standard mobile tool for pastors and staff.  I really hope F1 support for the iPhone is made a priority!

---

"Die before you die. There is no chance after."
-C.S. Lewis, Till We Have Faces.

OK, I tried to make a Data Exchange application with the iPhone SDK for Fellowship One and hit a wall, a pretty big one.  The framework that a mac would use for SOAP (Web Services) just wasn't ported over to the iPhone.  I hear there are ways(hacks) to do it still with the CFNetwork framework, but for someone who's never made anything for the Mac or iPhone, that's a pretty tall order right now.  However, I hear Apple is working on an example to get SOAP working in the way just mentioned.  'Til then...

 

EDIT

.....Because why would they include something a web app could do, took me a while. 

Can anyone at FT comment on whether the limitation lquigley is describing would continue to be a problem with the new REST API? 

 

 

---

"Die before you die. There is no chance after."
-C.S. Lewis, Till We Have Faces.

lquigley is correct, trying to implement / use SOAP probably will not work with that platform - unless it gets extended later on down the road.  Regarding DataExchange, it is purely SOAP. You can, however, work around the SOA of this SOAP Web Service and construct your own XML as a parameter (“sXML” being the request parameter) and submit the request via POST.

In the long run the RESTful API will definitely be the way to go.  Since it is strictly RESTful it assumes HTTP and that is really all it needs.  If your code can understand the basics constructs of HTTP actions (GET, POST [Low REST], PUT, DELETE [High REST]) and request / response then you’ll be up in no time.

DataExchange is strictly an XML based RPC so it will be difficult to use in a "web friendly" environment and is more keyed for machine to machine interaction - its primary purpose is to transport large amounts of data in and out of F1.  The RESTful API will be just the opposite; a full-fledged web/human friendly API built specifically for uses like those mentioned above.   

--Nick

Jared, I realize this is an older post but got my attention because I've been an iPhone owner/fanatic since first released. Very excited about new 3G. Always enjoy networking with other iPhone users particularly those involved in using technology for ministry purposes. Contact me if you desire. pastorkirby@wogcc.com.

Kirby Andersen