Let's face it: we all have great ideas for a web application. Whether you write them down on paper or remember them using your eidetic memory, there comes a point when you want test whether or not your idea is really viable.

In this tutorial, we'll use a micro framework, a templating language and an ORM to rapidly develop an application prototype.

If you are going to build an android application (it can be any other mobile platform or web too) that manages all the user data on a central database, REST API will be good architectural option to do the communication between the app and the server.

If you consider Evernote, Wunderlist apps, these apps can uninstalled at anytime and once we install them back and login, all our data will be restored. This is because all the data will stored in a cloud database and communication b/w app and database will be done using a REST API.

This tutorial gives enough knowledge about building a REST API for very beginners. As this tutorial seems lengthy, I had divided it into 2 parts. In the 1st part we learn fundamental concepts of REST and do the required setup. In the 2nd part building actual API (writing PHP & MySQL code) is covered.

Hi,

I would like to access th urlFor() helper directly in my view. Is this function exposed in the view. I couldn't see anything in the code. I guess I could just use slim::getInstance()->urlFor('blah'). Anyone have any better ideas? Or comments on this approach?

Thanks in advance.

Tony

OAuth can be anything you want it to be, the standards are lax and give you plenty of room for getting the right implementation for your system. However you proceed, though, you'll need to check an access token on every request - and in a Slim application, a middeware can help enormously since it hooks in to every request by design. I've recently implemented this and thought I would share.

Slim is a lightweight framework that packs a lot of punch for its tiny footprint. It has an incredible routing system, and offers a solid base to work from without getting in your way. Let me show you!
But that’s not to say that Slim doesn’t has some issues; it’s one-file setup becomes cluttered as your application grows. In this article, we’ll review how to structure a Slim application to not only sustain, but improve its functionality and keep things neat and systematic.

Hello

I have been busy trying to make a small website with a simple cms. It uses the twig for the layout.

I wanted the cms to have a login so after searching here and there, and after a bit off trial and error I came to a working system.
Although it works, I am not really sure if its a good approach or if there are any thins that can be better. Especially on the authenticate matter. Also I wonder if the authenticate function is necessary on the $app->put and $app->put routes.

Any thoughts on this code is appreciated.