Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 7863443
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 2, 20262026-06-02T23:29:02+00:00 2026-06-02T23:29:02+00:00

I am hearing that sencha in general, by the mere fact of using javascript,

  • 0

I am hearing that sencha in general, by the mere fact of using javascript, has performance issues on android devices.

I am familiar with limitations of the android webview object, but I was wondering if these performance claims have any merit, especially with Sencha Touch 2 being out

Although I don’t have a lower end android device, I was looking through the Sencha Touch 2 gallery and could not find free android apps very easily, so perhaps you can explain your experience with Sencha Touch 2 on Android and what you did to make it faster

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-02T23:29:03+00:00Added an answer on June 2, 2026 at 11:29 pm

    To my experience so far, there are some crucial points to keep in mind when developing Sencha Touch 2 applications with as best performance as possible:

    1. To optimize application startup time:

      • Compress your JS & CSS files. Remove any unused JS functions or CSS mixins (this can be easily done through SASS/Compass). For more details, please read this: http://www.sencha.com/blog/an-introduction-to-theming-sencha-touch
      • Load external JS files dynamically, there’s already a good topic here: What is the proper way to load an external javascript in Sencha Touch 2
    2. To optimize application performance:

      • Keep your DOM structure as small as possible. Inactive views should be destroyed (and dynamically added to your Container later if needed).
      • Avoid using too many CSS3 properties since they are very slow on Android devices.
      • For any scrollviews, overscroll should be disabled on Android. I’ve tested many Sencha Touch 2 applications on Android devices and overscroll causes badly unpleasant experience because of delays and lags. (tested on Galaxy Tab, Nexus S, and some HTCs)

    There’s also a topic here which is quite relevant to your concern:

    PhoneGap 1.4 wrapping Sencha Touch 2.X – What about performance?

    Hope it helps.

    edited on Feb, 12th 2014: It has been nearly 2 years since I posted this answer (i.e. more than 3 years I have been working with Sencha Touch) and I have to say that Sencha Touch performance on Android is sadly unacceptable. Sometimes I was stuck in the thought that I’m not fully mastering the best practices, but I think it’s not the reason. Or at least, it will took us years to develop a large-scale Sencha Touch app which has equal “look and feel” as native apps because the tricks take us so much time.

    So in shorts, if you are targetting iOS or your app is very tiny, it’s okay. But for big apps on Android, I personally don’t go with Sencha Touch.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I am creating an app on android but after hearing about sencha that it
I keep hearing that Android applications should try to limit the number of objects
I've been using WebServices at moving data across the wire and that has served
I keep hearing that PHP has overhead. For example a C++ int uses 4
So I've been hearing a lot about Node.js and javascript web apps in general.
I remember hearing that for performance a development machine should be 32 bit, while
i keep hearing that i shouldn't be using primary keys in my asp.net mvc
I'm hearing that is better to have one connection open upon app start up
I keep hearing that branching in git is so much easier than in SVN,
I'm hearing this alot, that you can develop an app in WPF and run

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.