After spending a ton of time in Ruby on Rails we're getting back into some more PHP projects. And ASP.NET. :) Granted, it would be nice to only stick with one language, but a lot of our projects tend to involve solutions and packages instead of a lot of ground-up coding.

Anyhow, this is mainly a link for me to check out later if we need it: Tyler Hall's Simple PHP Framework.

http://code.google.com/p/simple-php-framework/wiki/ExampleWebsites

http://groups.google.com/group/simple-php-framework

NuSoap is a very popular framework to make SOAP web services in PHP, but what about REST? Here's a list of PHP REST Frameworks or starter kits to kickstart your web service mojo.

• rest-toolkit
• PHP REST SQL
• mod-ndb (well more of an Apache-MySQL REST bridge)
• RESTful School Demo
• Konstrukt
• dbscript
• Tonic

Check out As Button Generator to make shiny buttons for your web sites. No PhotoShop for you!

I have to stop reading Raven's blog posts -- he had another post about how free iPhone apps help Apple sell iPhones, and I totally agree.

The varied and strongly useful functionality found in some of the top free apps really helps Apple keep the iPhone selling strong. I've run into many people who see me use AroundMe or Shazaam and suddenly want an iPhone, too. Anyone who has seen iPhone commercials knows how well they show off the many useful things you can do with an iPhone. That's something that really irks me about the new Blackberry commercials -- iPhone commercials show all the cool things you can do with your iPhone via the OS and the apps. Blackberry mentions the touch screen and vaguely notes that the Storm and Bold are "faster" and let you surf the web and check emails. Like there aren't already a million phones out there (smartphone or otherwise) that let you surf the web and check emails. Come on, Blackberry, are you going to go fully into the obvious and mention how you can make phone calls, too?

I was actually excited about the Storm and Bold opening up BB ownership, because there are some pretty cool apps for the BB (e.g. TellMe -- say "coffee" into the handset & it'll pull up coffee shops near you using GPS, no typing required). But honestly, I think BB is shooting themselves in the foot by refusing to go after anyone who isn't already a Blackberry owner, and it's a huge shame -- for people who don't like the iPhone (or don't like AT&T), the Blackberry could have been a sexy, appealing alternative if they only knew how neat it can be.

I was reading over Raven Zachary's O'Reilly post about turning ideas into execution and found the comments as interesting as the main post. In a nutshell, Raven mentioned that there are a lot of people with ideas for iPhone apps, but that building an iPhone application is too expensive (i.e. $125/hour) for many to capitalize on their ideas, and that the demand for iPhone developer talent far outstrips the supply. In the comments, however, were a number of apparently-experienced iPhone developers without enough work and expressing frustration that they're struggling to find clients willing to pay them even $50/hour.

This gaps between supply and demand is nothing new in any service industry, including the IT/software development world. Varying rates aren't just common in the iPhone world -- for example, I have have met US-based sysadmins and web programmers, some of whom charge $125/hour and some who charge $25/hour. Normally the $125/hour people are far more experienced than the $25/hour people, but not always. I suspect that iPhone rates are already drifting down into a varying range (instead of everyone getting $125/hour), and as others have noted, the fact that you can build an iPhone app already doesn't mean you can instantly charge anyone $125/hour. I have come across a number of clients who turned us down because they found someone willing to build them an iPhone app for $3000 flat. Did they end up with a crappy, late app? Possibly, but maybe not.

Even in our experience building mobile & social apps, we've found clients who have healthy budgets for whom we're a true bargain, while also finding clients with no capital looking for a $500 application. We've even gotten a few calls from offshore firms looking to outsource mobile development to us (we're in Portland, OR).

It's my belief that you can charge a lot per hour if 1) you are good, and 2) you can find clients willing and able to afford decent rates in exchange for reliable quality development.

#1 isn't always required, although if you can explain to your client that paying an experienced developer $100/hour for 10 hours of work is more effective than paying a junior developer $30/hour for 40 hours of work, then you're halfway there. Just like if you have an important or critical plumbing problem in your house, are you going to hire the seasoned veteran for $90/hour or the CraigsList special for $25/hour? Unfortunately, some clients only see the hourly rate (and not the total cost), while others have a certain budget or rate expectation already built in.

#2 is about networking, advertising, sales, careful client selection, and offering something worth the extra fee (because you're seen as an "expert" or have specialized skills). Getting a decent influx of clients and finding the ones that fit your offering is important. For us, we try to find clients that have established budgets and for whom on-time, quality, experienced, creative execution is worth the extra expense (although honestly we're more affordable than a lot of other development shops). It's no surprise that a few of our clients found us after being "burned" by other developers who were cheaper but either didn't deliver or went AWOL. Sometimes you can find someone very cheap who's also very good, but many times you're just gambing. Plus, hiring a developer at a super-low rate opens you up to the huge risk of that developer finding a better-paying contract halfway through your project. And if that happens, guess where he's going to focus more of his/her energy?

Also, I think #2 is sometimes difficult for developers, as it's full of soft skills, so a lot of excellent coders find themselves struggling to find clients willing to pay $50/hour while reading with some amazement about other programmers turning away work at $125/hour.

For a while the main Joomla! social networking plugin was Community Builder, which we've used for a large Joomla-based social network. CB is ok but fell short in some areas, and it was necessary to stitch together a number of other plugins to get a full SNS featureset. However, JomSocial was just released today (by Azrul, the makers of JomComment and other fine components) and looks to be a strong viable alternative to CB for building an open source social network. We're looking forward to working with JomSocial in the coming months and will relate our experiences as we get more in-depth. In the meantime, if you're looking to build an open source social network or add social media capabilities to your existing Joomla! site, feel free to contact us.

Elgg announced version 1.1 about a week ago. We looked at Elgg a while back when it was young and a bit more education-centric, but it has matured into an open source platform with a good adherence to standards such as OpenSocial and OpenID, as well as an API. Feature-wise it still falls behind some other platforms like phpFox, Handshakes, or Dolphin, but the price is good and the look is clean.

Tired of iPhone correcting your IM abbreviations and other words? Two ways to do it:

Retype it a few times

Tip: if you retype something twice, it'll stop autocorrecting it. E.g. if you try to send "np" as an SMS to someone, iPhone will autocorrect that to "no." So hit the delete key to erase the "corrected" word & retype it again. The iPhone will autocorrect it again, so delete it one more type & retype it, and it will stay. Third time's the charm. Plus, next time the iPhone won't autocorrect it at all, since it is now in the dictionary.

Note that sometimes I had to do the "third time's the charm" tactic twice before an unusual word would stay in the iPhone's dictionary & not get autocorrected anymore.

Click the Suggested Word Box

You can also click the "suggested word" box (anywhere in it, not just the X) to prevent the autocomplete and add the word to the dictionary.

I was talking iPhone webapps last night with some other developers & the discussion turned to Javascript debugging. Thanksfully, most mobile web apps don't use a lot of javascript (mainly because they should be simple apps & mobile devices don't have the horsepower to do tons of javascript). But still, I rooted around and this post from Christopher Hill about enabling javascript debugging in Safari with Drosera. However, it only works in the Mac version of Safari, and you should grab the nightly build to boot.

If you're testing on Windows, you can get by with Firebug/Firefox for heavy & initial debugging, and then using Safari's Developer tools (enabled in the Preferences->Advanced dialog) and Safari's javascript console to echo out debug statements using javascript code like this:

          
            if(window.console)
{         window.console.log("some
debugging text");     } 
        

A quick note to say that I'll be talking about iPhone webapp development at the PDXUX meeting tomorrow night, 7pm, at the downtown Portland Koin center. I'll talk about mobile UI design, implementation choices, and how to build a native-like web app for the iPhone using iUI and ASP.NET.

A very near-term heads up that I'll be participating in the RWW Live chat on mobile web development this afternoon at 3:30pm PST. I'm not yet sure how much focus will be on mobile web versus mobile native applications, but hopefully my perspective on web sites targeting handhelds and iPhones will be useful in rounding out the conversation.