- Posted by jfarrar on March 14, 2009
To start off with I must say that Ribbit has come a long way. I joined the beta program back in Nov 2007 and started messing around with the framework. After doing little with the framework for about a year or so I started re-learning the API and then updating some code examples I had built to be compatible with their 2.5 release. There were alot of great enhancements to the API with the 2.5 release. At the same time they released the version update they also announced a contest for developers.
I decided I was going to enter into the contest and see how it went. I made it into the 3rd checkpoint, but fell short of placing in the top 5. Further motivated, I created another application (SimpleSignal Phone) along with the my first application (mailFone) -- video after the jump. I enhanced my mailFone to include incoming screens as well as outgoing, and integrated Plaxo photos for a visual identification of incoming calls or outgoing calls.
So here are my two entries:
mailFone:
http://www.joedeveloper.net/ribbit/emailfone.html
SimpleSignal Phone:
http://www.joedeveloper.net/ribbit/simplesignal/JoeDeveloperSimpleSignal.html
It was really fun working with the Ribbit API and I know that I will use it more frequently and hopefully sell some apps.
Ribbit Ribbit!
Joe
0 comments
- Posted by jfarrar on January 3, 2008
I'm not the greatest when it comes to blogging. I guess it's just difficult to blog when you have so many things going on. I'm going to get better at it, but for the time being it appears there will be months between blogs <g>. Anyhow, I've recently starting reading up again about this new voip component for Flex called ribbit. I had registered way back in October when it was first being released as a beta to only developers. I never really got a chance to integrate it into anything. However, now that I've started reading up on it again and have some ideas to play around with it.
I kind of have a philosophy about developing with new stuff. I first of all like to read all of the documentation (twice) so that I get a good grasp of the classes, methods and properties so I am not constantly having to go back to the reference documentation. Then I like to build some really simple applications that illustrate most of the features of the component/api/platform. After I've developed and integrated most of the simple features and made a few working examples (widgets, simple webforms) it's time to start wireframing and diagraming a much larger scale application.
So enough with the way in which I like to go about development and back to the ribbit platform. This product is absolutely the most innovative technology solution that ties together both the UI and backend to present a pretty and powerful application framework. The best of both worlds. I started out developing in flash then moved to PHP then moved to ASP.NET, C#, VB.NET. I figure it makes sense to return to my favorite framework (flash/flex/actionscript) and develop some cool little applications.
Ribbit just makes a ton of sense when it comes to user friendly applications. Obviously because it allows the developer to focus on the development and the designer to focus on the design and not really have to worrying about cross platform issues. It speeds up development and design time in my opinion by 40%, depending on the complexity of the UI and functionality.
In the end I'm looking at developing some pretty cool applications around the Ribbit platform, but at first I'll just do some simple integrations into familiar platforms that I have developed in before. Looking forward to messing around with the API.
19 comments