On the AndroidHive site there's a recent tutorial (plus screencast) about combining PHP, MySQL and SQLite to act as the backend authorization for your Android application.

In my previous article Android Login and Registration Screen Design i explained designing the login and registration interfaces, but it has no functionality. In this tutorial i am explaining how to build complete login and registration system in android using PHP, MySQL and SQLite. Also this tutorial covers how to build simple API using PHP and MySQL.

The tutorial walks you through each step of the process:

• Creating MySQL Database and Tables
• Building PHP API Classes
• Starting Android Project
• Making the JSON Parser, SQLite Database Handler and User Functions Classes
• Designing the Screens
• Switching between Activities
• Finally Updating AndroidManifest.xml

If you want to get started quickly, you can just download the final result and go.

The latest episode of the "/dev/hell" podcast has been released - Episode 4: "The Cool Kids Club".

Our fourth episode is all ready for your listening pleasure. In this exciting episode we focus on "The Conference Experience" and discuss why programming conferences are so important to developers. Chris talks about why CodeMash was so awesome and the awesome talks full of awesomeness that he attended. Ed talks about his own experiences with speaking and attending conferences, complete with a total derail by Chris on why a certain conference rubbed him the wrong way. Oh yeah, you also find out our opinions on what constitutes a "well-written PHP application". I'm sure you will be surprised by our answers.

You can either listen to this latest episode either via the in-page player or you can download the mp3 directly.

On PHPMaster.com today there's a a new tutorial helping you take some first steps with CakePHP, a popular full-stack PHP framework, by Vito Tardia.

CakePHP is a framework that provides a solid base for PHP development. It allows users at any skill level to rapidly develop robust web applications. [...] Personally, the reason why I prefer CakePHP over other PHP frameworks is its better support for console applications. CakePHP has a powerful console tool that can be customized to build applications for both the web and the console world. In this article I'll introduce you to two of CakePHP's most useful features: automatic code generation using the console tool Bake and dynamic scaffolding.

He walks you through the full (user friendly) installation and configuration, a few changes to increase security and where to go to set up your database connection. From there he shows how to use the "Bake" command to generate a "subscribers" model and automatically create the user interfaces to work with it (CRUD operations)

On PHPBuilder.com today Jason Gilmore has a new tutorial showing how to create voice recognition applications with PHP and the help of open source voice interpretation tools.

Voice recognition or speech recognition technology is not easy to develop. In-house development would be very costly, and buying proprietary libraries that convert voice to text would make the developed application very expensive for end users. On the other hand, when developing in PHP, you have many open-source solutions available. The same dilemma happens with voice recognition in PHP -- there is an open-source class that can be used in voice applications. That way your application would cost less, and you also can offer it for free.

His tool of choice is Voice PHP, an open source project that uses four classes with support for SSML, SRGS, CCXML and VoiceXML. In his sample application he shows how to use the libraries to generate an application that can listen to a user's voice and translate that into certain menu options.

On NetTuts.com there's a recent post from Nikko Bautista about creating an API-centric application and how it can help you make a more flexible, accessible application overall. Code is included to make a simple TODO list application based on this idea.

Planning to start working on a new web application? In this tutorial, we'll discuss how to create an API-centric web application, and explain why this is essential in today's multi-platform world. [...] An API-Centric Web Application is a web application that basically executes most, if not, all its functionality through API calls. [...] Another characteristic of an API-Centric Web Application is that the API will always be stateless, meaning it can't recognize API calls by session.

He talks about how doing the work like this, though it might seem like more trouble up front, can lead to an easier time later when you need to add multi-platform support (or even open it to customers directly). In the sample application, he shows the creation of a TODO application that can create, read, update and delete items via an API. Also included is a bit of code to help secure your service with an APP ID and APP SECRET authentication set. Full code for the backend API and the frontend to interface with it can be downloaded here.

Josh Adell has posted a quick start guide to getting your application up and running on the PHPFog PHP platform as a service offering.

Being it was Christmas and all, I decided to give myself a present and sign up. I was very surprised by how easy it was to get up and running. I managed to build a simple "echo" service in about i.8 minutes, following roughly these steps.

It was as simple as "launching" a new custom application, waiting for it to become available, cloning the git repository and setting up a simple app. In his case , it's a basic Silex-based app that makes a simple site to greet users with a "Hello world" message. Throw in a basic .htaccess file and the app is all set to push.

Michelangelo van Dam is back with the second part of his series looking at running PHP applications on Azure (the first part Zend Framework.

Building web applications is nothing new anymore, as we've been doing it since the early days of the internet, but we've always done this on a single system. Even when Zend Framework came round, we kept doing the same thing and build apps for a single environment. But as I've discussed already in my previous article, developing for the cloud requires another approach. [...] With Zend Framework developing applications running on these separate compontents becomes really easy. It's like having your cloud toolbox right in your pocket.

He walks you through the settings needed to interact with a MySQL database backend, setting up sessions to write to the database, caching information to a memcache server and storing files on a remote destination (in this case cloud storage).

The Ibuildings techPortal has posted the latest episode of their recordings from this year's Dutch PHP Conference - Derick Rethans' talk "Profiling PHP Applications".

The web is full of useful advice focussed on pushing out the last bit of performance of your code. They mention trivial changes. like changing every occurrence of print with echo even suggesting to use for instead of foreach. These optimisations help, but you are not going to notice it unless they're in a tight loop with many iterations. It is also a wrong approach for tackling performance issues.

You can listen to this latest episode either through the in-page player, by downloading the mp3 or subscribing to their feed. You can also page through his slides as you listen.

In this new post to Reddit.com, the question is asked "Should I be doing just about everything using REST?" - wondering if their new applications should all sit on top of a web service for their functionality.

I'm pretty new to server-side programming, and actually started out with Python/mod-wsgi. From the ground up, mod-wsgi made a lot of sense. The server gets a request, you route the request. It feels like that's where I should start, so that's pretty much what I'm trying to create with PHP (a REST router - for learning purposes, I know frameworks exist). I'm trying to think of a situation where I wouldn't use a REST interface, but I can't seem to think of one (even for simple cases). Would it be safe to say that using REST is a pretty safe bet, most of the time?

There's some good discussion and answers to his question touching on things like Service Oriented Architectures, some implications of having a web service power an entire application (or applications) and a few comments with some personal experience.

A comment about SOA sums it up well:

You learn to write for your platform in the way developers/partners will have to, so you produce a good quality usable API which encourages development and consumption of your platform.

PHPFog, the PHP-centric platform as a service has made a new post to this blog about two new "gifts" they're providing to developers:

I want to thank you for your interest in PHP Fog. Thanks to you and tens of thousands of developers like you, we have grown massively in the last year and a half. As a sign of my gratitude, I'd like to give you two free gifts.

Their gifts to the community are a conversion of the 6 month applications over to a free-for-life product and you can now deploy three of these "free forever" applications instead of just the one. You can signup here for the service with offerings of installed software like PyroCMS, Drupal 7, MediaWiki and Slim. For more information, you can attend this webinar.