Live data from Hacker News

Chrome DevTools for Mobile: Screencast and Emulation

html5rocks.com

41–50 of 51 posts

Re: Chrome DevTools for Mobile: Screencast and Emulation

#41

Earlier quoted context omitted.

Right, but it's not uninstallable on many newer devices which also have the proper Android browser too, so these figures will be way off.

I suppose you are referring to devices like the new Nexus 7 that come with Chrome pre-installed. It doesn't have android's native browser and as far as I know it's the only device that ships with Chrome.

Nope, it's basically any device with the Play Store on running Android 4.2 or later.

Chrome being the only browser on Nexus devices has become another reason to avoid Nexus devices, along with the Hangouts as only messaging app and the general lack of storage. It's merely that the alternatives are arguably worse.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#42

Earlier quoted context omitted.

check out browserstack.com

This seems like the holy grail and I will definitely do the free trial to test it out but at this point I am not getting paid for my website development efforts so I'm not ready yet to pay a monthly fee for this (just hacking on something for myself).

You can get free screenshots for nine different browsers by using this link:

http://www.modern.ie/en-us/report

Re: Chrome DevTools for Mobile: Screencast and Emulation

#43
post #5

Earlier quoted context omitted.

You can remotely debug a Safari session on a device - but it has to be through desktop Safari. It's in the Develop menu.

I'm on Linux and installing a virtual box with a Safari browser just for that seems like too much trouble. I have access to my brother's iPhone but it's annoying for me and for him to have to push my changes to a staging site then go "hey can I use your iPhone for a second" every 5 minutes.

You don't need to push your changes to a staging server. Just have your computer and iPhone on the same wifi network. Then direct the iPhone's browser to your computer's IP address:port

e.g. 192.168:56:65:4000

Re: Chrome DevTools for Mobile: Screencast and Emulation

#44

Earlier quoted context omitted.

check out browserstack.com

This seems like the holy grail and I will definitely do the free trial to test it out but at this point I am not getting paid for my website development efforts so I'm not ready yet to pay a monthly fee for this (just hacking on something for myself).

What I did (before I got someone to pay for it for me :D) was buy an iPod touch on craigslist. Got it for like $80. It was a big stretch, financially, at the time, but the hours upon hours it saved was well worth it. You can also sometimes pick up iPhones with bad esns/cracked screens for a lower than normal cost.

'Course all of that assumes you would need more than 2 months worth of debugging on browserstack.

Good luck, either way

Re: Chrome DevTools for Mobile: Screencast and Emulation

#45

Earlier quoted context omitted.

I'm on Linux and installing a virtual box with a Safari browser just for that seems like too much trouble. I have access to my brother's iPhone but it's annoying for me and for him to have to push my changes to a staging site then go "hey can I use your iPhone for a second" every 5 minutes.

You don't need to push your changes to a staging server. Just have your computer and iPhone on the same wifi network. Then direct the iPhone's browser to your computer's IP address:port e.g. 192.168:56:65:4000

Ah yes of course that makes sense. Can you tell I'm a total newb :) Thanks.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#46

Earlier quoted context omitted.

This seems like the holy grail and I will definitely do the free trial to test it out but at this point I am not getting paid for my website development efforts so I'm not ready yet to pay a monthly fee for this (just hacking on something for myself).

What I did (before I got someone to pay for it for me :D) was buy an iPod touch on craigslist. Got it for like $80. It was a big stretch, financially, at the time, but the hours upon hours it saved was well worth it. You can also sometimes pick up iPhones with bad esns/cracked screens for a lower than normal cost. 'Course all of that assumes you would need more than 2 months worth of debugging on browserstack. Good l…

Yeah this is the way I'll end up going. Less than a $100 is a small investment to make sure my sites show well on such a large segment of devices.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#47

I'm not seeing the screencast icon. (chrome 32/ubuntu desktop, chrome 31/android 4.1)

Chrome 32 Beta on android ( https://play.google.com/store/apps/details?id=com.chrome.bet... ) is necessary. I'll update the post to make that clear. Thanks.

Thanks.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#48

I'm not seeing the screencast icon. (chrome 32/ubuntu desktop, chrome 31/android 4.1)

Chrome 32 Beta on android ( https://play.google.com/store/apps/details?id=com.chrome.bet... ) is necessary. I'll update the post to make that clear. Thanks.

So WebViews in KitKat are not screencast-able as they are currently pegged at Chromium 30. Nevertheless, a debuggable WebView is an enormous leap forward in Android Web development.

I found: https://developers.google.com/chrome/mobile/docs/webview/ove...

  Your apps inside a WebView are just as important
  and deserve a runtime that keeps users up to date.
  There are large engineering and logistical
  challenges. We're not quite there yet, but we're
  working on it.
I presume that the engineering feat is getting WebViews packaged in an updatable form. Right now WebViews are linked through the Android system, exposed as Java classes to apps... code that is not contained in APKs.

I can think of two ways to solve this:

1) Android learns how to receive partial system updates outside of device and carrier certification processes (maintenance releases). Through the Play Store, for instance.

2) WebView architecture is changed to run WebViews as a service hosted in a dedicated WebView app, upgradable as an APK. This would require either an enhancement to RemoteViews or a new solution altogether.

Re: Chrome DevTools for Mobile: Screencast and Emulation

#50

Earlier quoted context omitted.

Chrome 32 Beta on android ( https://play.google.com/store/apps/details?id=com.chrome.bet... ) is necessary. I'll update the post to make that clear. Thanks.

So WebViews in KitKat are not screencast-able as they are currently pegged at Chromium 30. Nevertheless, a debuggable WebView is an enormous leap forward in Android Web development. I found: https://developers.google.com/chrome/mobile/docs/webview/ove... Your apps inside a WebView are just as important and deserve a runtime that keeps users up to date. There are large engineering and logistical challenges. We're not…

>1) Android learns how to receive partial system updates outside of device and carrier certification processes (maintenance releases). Through the Play Store, for instance.

That's what google is doing with the Google Play Services 'super app' - it's meant to untie Android API updates from carriers. With the bonus of the app being closed source and thus not part of stock AOSP.

Post reply on HN