4 Answers

• Hi
  Yes, the ipod is slow ( I have one too :) )
  But there are optimisations you could do

  Do you use a className for tablerows?

  If you have multiple windows create the elements inside each window only when are needed.

  If you have elements displayed only once remove it after this.

  If you use sounds, after they are played and not needed anymore remove it

  Don't use transparency/opacity. Set each element backgroudColor if you have a solid color behind. Try not to use rounded corners.

  Don't use webviews if possible.

  Lots of "don't" :)

• Well, there is a post around with tips and tricks that I started but seems not to have too much love from the developers :)

  http://developer.appcelerator.com/question/5291/tips-and-tricks-mobile—thread-to-share-some-experience-that-may-help-the-others

  ps. thanks for your kind words :)

• any advices on images?

  I've noticed for example that using imageViews with a size diferent from the original image is a slower operation (probably because of the auto-size).

• I try to bring the "best practice" from the web to Ti as much as possible.

  So I try to provide the images at the exact size, and optimised with this tool: http://imageoptim.pornel.net/

  Don't mind the url :)

  Less pixels and info to load, faster the imageView,

  I also try to avoid "auto" or to force the device to make the calculation

  So instead of:

  top:10,
  left:10,
  bottom:10,
  right:10
  

  I do:

  top:10,
  left:10,
  width:300
  height:460
  

  assuming a fullscreen mode( 320x480)

  use jpg where it's possible instead of png, and so on :)