Sencha is pleased to announce the release of the latest version of our SDK that allows developers to utilize AT&T APIs from within an HTML5 application. This release of the SDK builds upon the previous release by including Sencha Touch 2 and adding access to new APIs such as Speech and In App Messaging from Mobile Number (Beta).
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.
One of the first questions I always hear when starting with a new client is “How can I build unit tests for my application?”
It’s obvious that many people understand the benefits of unit tests – developers want to minimize the number of bugs in their code and managers want to reduce the amount of time required to test an application before release. Although the concept of unit testing has existed for years, software teams are only now beginning to explore building tests for their Rich Internet Applications (RIAs).
Today we’re releasing the Sencha Touch oData Connector for SAP, available on the Sencha Market. We’ve partnered with SAP to make it easier for SAP customers to build HTML5 applications using Sencha Touch. We announced our partnership with SAP earlier this year and have been working actively with SAP to build this shared capability to make it easy for developers to quickly build rich mobile enterprise applications.
Extensions provide developers with valuable features beyond those that ship in Sencha’s frameworks, and are a very important part of the Sencha platform. At Sencha, we are investing to improve the ecosystem of extensions on our platform and I wanted to share an early look at our progress.
The Sencha.io photo sharing example shows you how to use Sencha.io, the Sencha cloud service, with your Sencha Touch 2 mobile apps.
In this article, we’ll show you how to take advantage of Sencha.io in a Sencha Touch application. We’ll use two of the Sencha.io services — the User Login service to have users connect to the app via Facebook, and the Data service to store information.
Today we are excited to announce the launch of another fine Sencha Touch 2.0 example application, Discover Music, which was designed and created by Modus Create, a Sencha partner.
In the previous series of articles Part 1, Part 2, and Part 3, we explored architecting a Pandora-style application using the new features of Ext JS 4. We started by applying the Model-View-Controller architecture to a complex UI that has multiple views, stores and models. We looked at the basic techniques of architecting your application, like controlling your views from Controllers and firing application-wide events that controllers can listen to. We also discussed how to get references to views, controllers, models and the application itself. Lastly, we implemented several controllers to get a feel for how to implement basic application logic.
In Sencha Touch 2, we introduced the newest iteration of our MVC architecture. Based on the same concepts found in the Ext JS 4 and Sencha Touch 1 MVC package, we have simplified existing features like control and reference syntaxes, and introduced new functionality like routes and history support.
In this article, we will take the existing code we have created and upgrade it to use Sencha Touch 2 and the updated application architecture. We will discuss some of the differences in syntax and talk about some of the new concepts to consider. At the end of this article, you should be better prepared to go into your existing Sencha Touch 1 app and upgrade it to Sencha Touch 2, provided it is architected based on the principles discussed in the previous articles.
That application you just deployed? As experienced software developers, we all know it won’t be long before you’re going to need make to significant UI changes. Regardless of the amount of painstaking forethought, consensus gathering and planning backing it, no software design ever survives first contact with its users unscathed. To deliver truly effective software, we have to be prepared to adapt to an evolving understating of our users’ needs.