Sencha Inc. | HTML5 Apps


Meetcha—Using Sencha Touch to Build a Mobile App for

August 23, 2012 | Ashvin Radiya

Guest Blog Post: Dr. Ashvin Radiya, President and CTO of AvantSoft, Inc.

Meetcha App


We developed the Meetcha app to demonstrate how to use Sencha Touch 2 features in a real world application. We used the Sencha Touch’s built-in MVC architecture, which we’ve found in this app and in general is absolutely required for developing large commercial applications. We also wanted the Meetcha app to have an engaging UI, so we used custom theming to create rounded buttons and non-rectangular positioning with a custom background that changes with orientation. This app also illustrates how to create context-sensitive navigation by showing the map of the meetup or home screen depending on how soon the event is taking place.

In this article, we explain the development techniques behind the following features of the Meetcha app to help you build apps in Sencha Touch 2.

  • Overall Class Structure
  • Building an Orientation-Aware UI
  • The Power of Contextual Navigation
  • Using OAuth for Authorization
  • Calling the API
  • Creating Lists with Action Buttons
  • Using Dynamic forms
  • Putting Local Storage To Work
  • Using Plugins for Pagination

Overall Class Structure

The Meetcha application follows the standard Sencha MVC structure. The app folder contains the miscellaneous, controller, model, store and view classes. The resources folder contains the scss folder which is compiled into resource/css/app.css.

Controller Folder
The controller folder contains the controller class for various screens.
Model and Store folders
The model and store folders contain classes for models and stores that power the data to the application.
View folder
And finally, the view folder contains classes for various views.

Building an Orientation-Aware UI

The first feature that we’ll discuss is the orientation-aware UI. Many mobile apps are “boxy” with rectangular and grid-like arrangements of elements. We wanted to create an engaging UI by breaking the pattern of “rectangles” and “grids” that respond to the orientation change. There are three moving parts that you need to consider to enable this feature:

  • Custom background that changes with orientation
  • Rounded buttons
  • Reposition buttons on orientation change

Let’s take a look at how we can achieve this with Sencha Touch.

First, different images are referenced as backgrounds in two CSS classes: home-landscape and home-portrait in app.scss.

.home-landscape > .x-body {
    background: url('../images/meetcha_screen_bg_landscape.png') top left no-repeat;

.home-portrait > .x-body {
    background: url('../images/meetcha_screen_bg.png') no-repeat;

Next, the radial glow effect is produced by setting a CSS class for the container of the buttons in _buttons.scss.

.button-container {
    @include radial-gradient(color-stops(rgba(196,0,0,1) 0%, rgba(92,0,0,1) 100%));
    border: 0 !important;
    margin: 0 !important;
    padding-left: 20px;   

The rounded effect of the buttons is created by styling the background, border-color, border-radius, width, height, z-index, button label and button icons.

.home-button {
    @include box-shadow;
    background-image: none !important;
    background-color: rgba(196,0,0,1) !important;
    border-color: #990000;
    @include border-radius($button-height * 2);
    width: 100px;
    height: 100px;
    z-index: 0 !important;

    &.mygroups, &.findmeetups {
        width: 120px;
        height: 110px;

    .x-button-label {
        color: #fff;
        font-weight: normal;
        font-size: 14px;

    .x-button-icon {
        width: 4em;
        height: 2.5em;
        background-repeat: no-repeat;
        -webkit-mask-repeat: no-repeat;
        margin-top: 5px;

.findmeetups, .mygroups, .findgroups {
    .x-button-icon {
        margin-top: 0.7em;

Next, we define buttons to have different positions and background class for its container based on the orientation in doOrientation( ) in Meetcha.view.HomeScreen class as follows:

Ext.define('Meetcha.view.HomeScreen', {
    extend: 'Ext.Container',
    xtype: 'homescreen',
    config: {
        xtype: 'container',
        cls: 'button-container',
        defaults: {
            iconAlign: 'top',
            margin: 10,
            top: 0,
            left: 0
        items: [{
            xtype: 'button',
            cls: 'home-button findmeetups',
            pleft: 18,
            ptop: 40,
            ltop: 0,
            lleft: 48,
            iconCls: 'find-meetups',
            text: 'Find Meetups',
            action: 'findmeetups'
        }, //...more buttons

    initialize: function() {
        this.on('painted', this.doOrientation, this);
        Ext.Viewport.on('orientationchange', this.doOrientation, this);

    doOrientation: function() {
        var me = this,
            orientation = Ext.Viewport.getOrientation(),
            letter = orientation.charAt(0),
            items = this.getItems().getRange(),
            i = 0,
            ln = items.length,
            item, el, top, left;

        me.element.addCls('home-' + orientation);
        for (; i < ln; i++) {
            item = items[i];
            top = item.initialConfig[letter + 'top'];
            left = item.initialConfig[letter + 'left'];
            el = item.element;
            if (el) {
                    top: top,
                    left: left

The Power of Contextual Navigation

To make applications more usable, it’s important to create a user flow that is “contextual” by presenting relevant information to the user with appropriate navigation choices. In the Meetcha app, we show different screens to the user based on when the application is launched. If it’s within two hours of the meetup time, the user is most likely looking for the meetup map, so we show the Next Meetup screen; otherwise we show the Home Screen. From the Next Meetup screen, the attendee can tap on the At Meetup button at the bottom to check in. The logic is in controller.HomeScreen.js.

decideWhatToDo : function(){
    var me         = this,
    upcomingEvents = Ext.create(''),
    user           = me.getApplication().getController('User').getCurrentUser(),
    dt             = new Date(),
    inTwoHours     = Ext.Date.add(dt, Ext.Date.HOUR, 2);

        params : {
            member_id :,
            time : dt + ',' + inTwoHours
        callback: function(records){
            if(records.length > 0){
                    xtype: 'loadmask',
                    message: 'Upcoming meetup(s) found.  Loading Map'
            } else {

Using OAuth for Authorization requires OAuth for authorization. The OAuth protocol requires a callback from the server to the client, which means it can’t be called directly from the Sencha Touch app. We built an intermediate layer using PHP to support OAuth and make calls to the server to retrieve data. The PHP code is hosted on the Sencha servers and we provide all the relevant parts here in this blog post. One of the key requirements of the app design was to avoid asking the user to authorize with every time the app launches, so we achieved this by storing authorization information in a cookie. Here’s how we did it:

  • During the app launch, perform the authorization check.
  • When the app is accessed for the first time, prompt the user to authorize the Meetcha application on Set the authorization details in a cookie.
  • For any subsequent launches, use the authorization details from the cookie to access the user details.
  • If a user logs out, then clear the cookie.

The following screens show the user interactions for OAuth authorization in the Meetcha app.

We’ll explain some of the key concepts we used with OAuth authorization.

How to Set a Cookie on Your Server

In the Meetcha app, we set the member_id and other authorization information in a cookie after successful login and Meetcha app authorization.

$thirtydays = time()+60*60*24*30;
setcookie('oauth_token', $oauth_token_per, $thirtydays, '/');
setcookie('oauth_token_secret', $oauth_token_secret_per, $thirtydays, '/');
setcookie('member_id', $member_id, $thirtydays, '/');

How to Check for a Cookie on Your Server

The first time a user logs in, the code returns -1 since there is no member and authorization information found in the cookie. For subsequent calls, the code returns member ID info in the cookie.

if($_COOKIE['member_id'] && $_COOKIE['oauth_token'] && $_COOKIE['oauth_token_secret']){
    jsonEcho(json_encode(array('results' => array('id' => $_COOKIE['member_id']))));
    jsonEcho(json_encode(array('results' => array('id' => -1))));

Logic for Authorization in Meetcha.controller.User

When the app launches, it loads the User model (which communicates with user_check.php). If the User model is loaded successfully (based on the previous authorization state) for a valid user, then it shows the application home screen; otherwise it shows the Welcome screen to authorize the user.

    launch: function() {
        var me = this;
        Meetcha.model.User.load(1, {
            success: function(rec) {
                var id         = rec.get('id'),
                    app        = me.getApplication(), 
                    homeScreen = app.getController('HomeScreen');
                    docked: 'top',
                    xtype: 'meetchatitlebar',
                    title: 'Meetcha'
                if (id == -1) {
                } else {
                        id: id

Calling the API

The API documentation describes how you can use their API to access Meetup data from your application. It accepts HTTP GET request to receive information for meetup events, groups, comments, meetup venues, RSVP, check-ins, member profiles, etc; and it accepts HTTP POST to add a new meetup, do meetup check-in, do RSVP, create profile, add photos, etc. The typical structure of the API call is as follows:<<methodName>>.<<responseDataFormat>>?<<setOfRequestParams>>&<<API_Key>>

The Meetup API supports authentication for third-party applications; the Meetcha app uses the OAuth protocol which requires a callback, so we created a PHP wrapper to the API with the following features:

  • Built to communicate with for accessing the Meetup data based on Meetcha consumer API key.
  • Uses OAuth as an authorization protocol to access user’s information securely.
  • Upon authorization, sets the OAuth token and secret as a cookie, so it can be used for various API calls.
  • Makes GET requests to query meetup data like group, events, members, rsvp, etc.
  • Makes POST requests to add/edit the event details, comment, rsvp and check-in information.

As an example, here is the code snippet of 2_events.php, which is a wrapper to call the events API on Meetup (at this endpoint:

require_once ("OAuth.php");
require_once ("config.php");

$time = readGetParam('time', null);

$offset = readGetParam('page', 0) - 1;
$meetup_url = ''.$member_id.'&page='.readGetParam('limit', 20).'&offset='.$offset;
if($time != null){
    $meetup_url .= '&time='.urlencode($time);
$signature = new OAuthSignatureMethod_HMAC_SHA1();
$consumer = new OAuthConsumer($key, $secret, NULL);
$token = new OAuthConsumer($oauth_token_per, $oauth_token_secret_per, 1);
$request = OAuthRequest::from_consumer_and_token($consumer, $token, "GET", $meetup_url);
$request->sign_request($signature, $consumer, $token);
$header = $request->to_header("");

error_log('2_events_URL:' . $meetup_url);
$meetup_response = _http_request($meetup_url, $header);


In the Sencha Touch app, the URL to the server side PHP is set in the Store’s Proxy, or in the Ajax call in the controller to retrieve the data.

Creating Lists with Action Buttons

In this section, we explain how to build custom lists with action buttons. This will be useful to many developers, as it’s a very common requirement.

There are many similar lists in our app such as Find Meetups, My Meetups, etc, so we created a abstraction called MultiActionList and put the common code in a base class. A derived class has the responsibility of defining an itemTpl with <a> elements as well as “action” and “store id” attributes. In the base class MultiActionList, the event handler for tap will fire a new event, passing in the data record behind that list item. Below is the code from MultiActionList class.

Ext.define('Meetcha.view.MultiActionList' ,{
    extend : 'Ext.dataview.List',
    initialize : function() {
            function(event, target) {
                var action  = target.getAttribute('action'),
                    id      = target.getAttribute('mu:id'),
                    record  = id && this.getStore().getById(id);

                this.fireEvent('actionTap', this, action, record, event, target);
                delegate: 'a[action]',
                element: 'innerElement'

In a subclass, such as Meetcha.view.MeetupList, itemTpl is defined with <a> elements which are styled to look like a button.

Ext.define('Meetcha.view.MeetupList', {
    extend: 'Meetcha.view.MultiActionList',
    config: {
        itemTpl: Ext.create('Ext.XTemplate',
            // Right Column
            '<div class="ml-rsvp">',
                '<tpl if="!self">',
                    // RSVP action section
                    '<a class="add-btn button" href="javascript:null;" action="join" mu:id="{id}">RSVP</a>',
                '<tpl elseif="this.hasWait(values)">',
                    // Wait List
                    'Wait List',
                '<tpl elseif="this.hasRsvp(values)">',
                    '<tpl if="this.isAttending(values)">',
                    // Attend + Cancel action section
                    'Going<br/><a class="checkmark-btn button summary-cancel" href="javascript:null;" action="cancel" mu:id="{id}">Cancel</a>',
                    '<tpl else>',
                        // Attend action section
                        '<a class="add-btn button summary-rsvp" href="javascript:null;" action="joinDirectRsvp" mu:id="{id}">RSVP</a>',
                '<tpl else>',
                    // Attend action section
                    '<a class="add-btn button summary-rsvp" href="javascript:null;" action="joinDirectRsvp" mu:id="{id}">RSVP</a>',

Then, a controller for this view can handle actionTap event and take appropriate actions. For example, the MeetupList controller class uses the actionTap handler for processing requests for Join a group or attend a meetup.

Ext.define('Meetcha.controller.MeetupList', {
        control: {
            'meetuplist': {
                actionTap: 'onActionTap'
    onActionTap: function(list, action, record, event, target) {
        switch (action) {
            case 'join':
            case 'attend':

    promptForJoinAndRsvp: function(record) {
        Ext.Msg.confirm('Join Group and RSVP', 'Please click yes to join the group and RSVP.', function(buttonId) {
            if (buttonId == 'yes') {
        }, this);
    rsvp: function(event_id, event_name, rsvp) {
        var me      = this,
            rsvpURL = serverUrl + 'php/submit_rsvp.php';

Using Dynamic Forms

In many applications, there’s a practical need to generate dynamic forms. In Meetcha app, before a user can RSVP for a meetup, they must join the hosting group which in turn can optionally require the user to answer several custom questions as shown below.

A different group may present a different set of questions.

Below, in Meetcha.controller.MeetupList, we check to see if the group has questions. If it has questions, then we instantiate a view with xtype joingroupquestionspanel.

Ext.define('Meetcha.controller.MeetupList', {
     * Some meetups require the user to answer questions before joining the group.
    checkForGroupQuestions: function(record) {
        var me = this;{
            url: serverUrl + 'php/2_groups_by_group_id.php',
            method: 'GET',
            params: {
                group_id: record.get('group').id
            success: function(result, request) {
                var eventId   = record.get('id'),
                    eventName = record.get('name'),
                    results   = result.results[0];

                if (results.join_info.questions_req == '1' && results.join_info.questions) {
                        xtype: 'joingroupquestionspanel',
                        event_id: eventId,
                        event_name: eventName,
                        group: results
                } else {
                    this.joinAndRsvp(eventId, eventName, results);
            scope: this,
            record: record

Next, in Meetcha.view.JoinGroupQuestionsPanel, using the initialize() function, we iterate through a list of questions and add a pair of items for each question—a component that shows the question text with a textfield for the user to enter the answer to that question.

Ext.define('Meetcha.view.JoinGroupQuestionsPanel', {
    extend: 'Ext.form.Panel',
     * Populate the questions etc that this panel needs from the configuraiton
    initialize: function() {
        var me             = this,
            group          = this.getGroup(),
            grpName        = Ext.util.Format.ellipsis(, 20, false),
            questions      = group.join_info.questions,
            i              = 0,
            questionFields = [], 

            xtype: 'toolbar',
            docked: 'top',
            itemId: 'topToolbar',
            title: grpName

        if (questions) {
            for (; i < questions.length; i++) {
                q = questions[i];
                    xtype: 'component',
                    html: q.question,
                    cls: 'question-label'

                    xtype: 'textfield',
                    ui: 'dark'

Putting Local Storage to Work

Local storage is another very common requirement for Sencha Touch apps. In the Meetcha app, user preferences are stored in localStorage. To find a meetup, the user can choose whether to use their current location, a preferred zip code and distance within which to find a meetup, and interests. User preferences are also stored for finding groups.

This is very easy to achieve in Sencha Touch by declaring localstorage as proxy type in Meetcha.model.FindSettings model.

Ext.define('Meetcha.model.FindSettings', {
    extend: '',
    config: {
        idProperty: 'id',
        fields: [{
            name: 'Location',
            type: 'boolean'
        }, {
            name: 'ZipCode',
            type: 'string'
        }, {
            name: 'Distance',
            type: 'string'
        }, {
            name: 'Time',
            type: 'string'
        }, {
            name: 'Interests',
            type: 'string'
        proxy: {
            type: 'localstorage',
            id: 'findSettingsId'

Using Plugins for Pagination

The pagination is straightforward to add to a Sencha Touch app. In the Meecha app, we used two Sencha Touch 2 plugins to support pagination for various lists to show meetup events, groups and group members.

    Ext.plugin.PullRefresh (xtype: pullrefresh) makes a load request to the Meetup store when the user pulls down the list. Ext.plugin.ListPaging (xtype: listpaging) makes a load request to the Meetup store when a user scrolls to end of the list.
# Meetcha.view.MeetupList
Ext.define('Meetcha.view.MeetupList', {
    extend: 'Meetcha.view.MultiActionList',
    alias: 'widget.meetuplist',
    requires: 'Ext.plugin.PullRefresh',
    config: {
        emptyText: 'No Meetups found',
        cls: 'meetup-list',
        loadingText: 'Loading Meetups...',
        plugins: [{
            type: 'pullrefresh',
            pullRefreshText: 'Pull down to refresh meetups!'
        }, {
            type: 'listpaging',
            autoPaging: true,
            loadMoreText: ''
        itemTpl: Meetcha.classes.SharedTemplates.meetupSummary

How to Download and Run the Application

You can download the source files of Sencha Mobile application with PHP files from the following URL—

To run this application, you need to deploy both the Sencha Mobile application and PHP scripts that communicate with using OAUTH. You can deploy both on the same server or different servers. The Meetcha/php/readme file has the detailed setup instructions. As explained in the readme file, you will need to (1) create an application on and set your OAUTH consumer key and secret in Meetcha/php/config.php, (2) host PHP files on a server and set post-authorization destination URL in Meetcha/php/index.php, and (3) set up the files of Sencha mobile application on a server and point the serverUrl in Meetcha/index.html to the PHP server.

Conclusion and Future Extensions

We encourage and invite community members to make extensions to this app and contribute more cool techniques that others can view in the context of a real world application. Some of the ideas for extensions include:

  • Add animation effects when buttons are tapped on the home screen using Sencha Animator.
  • Add features to support attendee interactions around a meetup. For example, view checked-in attendees of the meetup, post messages to the meetup attendees, personal chats between attendees at the meetup, create profiles to be shown for a specific meetup, etc.
  • Use the Sencha Touch Native Packager to capture and post photos.
  • Store Meetup and Group data in local storage and refresh only as needed, so the app is usable in offline mode.
  • Use Sencha Charts to present meetup statistics.

You can build cool apps with Sencha Touch! Get out of the “rectangular” design mindset and start building apps that are easy to use with contextual information and navigation. Users will be delighted, and you’ll have more fun developing the app. Just like we did!

There are 11 responses. Add yours.

Karl Shea

2 years ago

Why do none of the big example apps use routes or history support?

(I mean other than the obvious reason that lots of the controls (like TabPanel) don’t really let you use routes without hacking around how they work)


2 years ago

Thx. This is quite a comprehensive example with lots of useful information.
Most tutorials leave you with questions when you start with real world stuff.


2 years ago

Great example of an app.
But I still don’t get the part where the user leaves the app to authorize it using oauth.

How do they do that? And how the user gets back to the app? Is it using an external window or something?

Ashvin Radiya

2 years ago

@ Fred - Thanks.

@Karl - History/routes/deep linking are very useful for a “Mobile Web Site” where there is a need to support browser back/forward as well as bookmark any page on the site for a revisit. In a Mobile App running on the device without the browser toolbar, the deep linking is useful when the user needs to be taken to the same page upon the app relaunch. One additional point to consider is that when using the routes, one can pass only simple set of tokens to a screen, whereas through a controller one can pass arbitrarily complex data to a screen. With that as a backdrop, in the Meetcha app, the user does not go back to the last visited page, instead the context driven design takes takes the user to an event that is about to happen or a list of upcoming meetups. Nevertheless, it would be good to illustrate routes, and if you are inclined to do so, we would greatly welcome that contribution!! Thanks for the suggestion.

@Matias - requires OAUTH which means that the will make a callback to our app. cannot call back directly into a pure client side Sencha Touch App running on a device. For a call back support, we need to run the PHP scripts on a server. calls back to this app’s PHP script on the server which in turn redirects to our Meetcha App. The php/readme file explains the parameters that have to be set including the redirect URL.


2 years ago

Loved this showcase… especially for the OAuth example code. Android is a significant portion of the market, but this example (and others) seem to ignore the cross-platform capabilities of the framework. I would love some perspective on this if you care to comment @Ashvin.


2 years ago

Thanxx a lot This is quite a comprehensive example with lots of useful information.
i found it useful

Alexander Evan

2 years ago

Logical Design DBS helps you leverage Drupal CMS to quickly deploy powerful mobile and desktop websites.
For more information visit


2 years ago

Hi, Great tutorial!  I’m new to Sencha Touch 2 but this tutorial is giving me a lot of insight.  Thanks very much.  I’m having a bit of trouble deploying it on to an android device, however.  Everything works fine in the web view (e.g. deployed on a local server) with an external php server.  Works great!  However, when I deploy it to an android device, the call back from authorizing hits the meetcha home url.  What should that be, if you’re deploying to a device?  Should it be my external php server’s url?  Right now, I can grant it permission, but then the browser comes back with a page not found, because my localhost isn’t reachable on my device.  Any thoughts?

TechMD Computer Repair

2 years ago

Just started learning mobile app programming… this is a great guide for several useful functions


2 years ago


Mobile Application Developer India

2 years ago

Hi there. Your writing is a great post for me. Thanks to share wit us.

Comments are Gravatar enabled. Your email address will not be shown.

Commenting is not available in this channel entry.