On a larger system level, yes we should.

Unlike PC's where it is just as easy to click on any part of the screen, the same is not true on a smartphone.  Most people are right handed, and are likely to hold the phone in their right hand and use their thumb when they are only using one hand. 

That makes the area of the phone swept from the bottom left to the top right the easiest to reach, and should be the area that is most used.  

It is also largely why this area is favoured in both iOS and Android design patterns for the phone (bottom left) and action buttons (usually top right).

Edit:
Now considering that applications already are geared for right handed people, I would argue that you should not optimise for individual handedness.  Quite simply because even left handed people will be used to right handed optimised smartphones and apps, so changing that will simply break the paradigm that they are used to. You may be offering a slight design improvement but with it would come a huge expectation penalty.

Smartphones are still usable with your left hand, and so breaking peoples expectations would present a worse UX.  Not to mention the additional cost and development time.

Should you optimize mobile experiences based on individual handedness?
I'm busy writing my first plugin, using PHP 5.3.5. I come from a C# environment, and I must say I'm more than happy with the level of support for good, solid OOP techniques in PHP. However, I'm a little uncertain how to structure a plugin using classes. I have a plugin class that takes care of hook registration in its constructor, and some worker classes like a mail queue and mailer, but I have one or two non-class scripts, mostly for forms, that I don't quite know how to neatly fit into classes. What resources are their I can consult for guidance on this aspect of my OO plugin?

The plugin is for mass mailing, i.e. mailing to all subscribers, on schedule etc. It registers a custom post type for mail templates, with add new and edit capabilities, and it adds its own menu to the bottom of the admin menu, currently with two submenu pages: 'settings' and 'send mail'. It also adds an 'opt out' option to the user profile page, but that's quite tidy and easy to include the main plugin class.
