The remote debugging is long past due. If google wants to push the mobile web and Android they need to step it up. Their browser is awful compared to the iphone's and the tooling isn't there. It's a place Android could really excel and, as a mobile web dev and Android user, it's been really disappointing to watch them sqaunder the opportunity.
Huh? They do need to step it up if mobile web apps are ever going to be a decent experience, the Android browser has been sometimes sufficient but never stellar, but isn't "stepping it up" exactly what remote debugging (and the new chrome) is? How is that squandering anything? Are you just mixing tenses?
Comments
The remote debugging is long past due. If google wants to push the mobile web and Android they need to step it up. Their browser is awful compared to the iphone's and the tooling isn't there. It's a place Android could really excel and, as a mobile web dev and Android user, it's been really disappointing to watch them sqaunder the opportunity.
Huh? They do need to step it up if mobile web apps are ever going to be a decent experience, the Android browser has been sometimes sufficient but never stellar, but isn't "stepping it up" exactly what remote debugging (and the new chrome) is? How is that squandering anything? Are you just mixing tenses?
Mobile safari certainly isn't a good example for tooling, though remote debugging is apparently there waiting to be enabled: http://atnan.com/blog/2011/11/17/enabling-remote-debugging-v...
> but isn't "stepping it up" exactly what remote debugging (and the new chrome) is?
Yes, which is why I said it's long past due.
I am using adobe shadow and it works well for my needs. Not sure for web apps debugging though. http://labs.adobe.com/technologies/shadow/