Skip to main content

Adobe Shadow: Testing your mobile apps

Adobe Shadow

 

 

“Adobe® Shadow is a new inspection and preview tool that allows front-end web developers and designers to work faster and more efficiently by streamlining the preview process, making it easier to customize websites for mobile devices.”

 
Features
  • Synchronized Browsing and Refreshing (Device Pairing) — Wirelessly pair multiple iOS and Android devices to your computer . With Shadow, you browse in Chrome, and all connected devices will stay in sync.
  • Remote inspect your code — Remote inspection and debugging capabilities. Target a device for remote inspection and using familiar development tools, make changes to your HTML, CSS and JavaScript and see your device update instantly.
  • Localhost URL support — Shadow now works correctly with URLs containing localhost, and 127.0.0.1. On Mac OS X, it also works with machine.local.
  • Adobe Edge integration — If you are using Adobe Edge, the Preview in Browser command now works with Shadow. You will see your animations previewing in Chrome, and on all of your Shadow devices. Note: This requires Chrome to be the default browser.
  • HTTP Authentication support — Now you can browse to URLs that require HTTP authentication, and see the login/password form on Shadow devices. If your URL contains the login id/password, Shadow devices will authenticate without the form. (e.g., using a URL like: http://login:password@mysite.com)
  • Improved workflows for sticky caches — You can now use a Refresh gesture on Shadow devices (tap on the page, hold, and pull down until you see the "Release to refresh..." message). This will reload your page, using the freshest assets.
  • URL Monitoring — Pages/apps that change URL parameters or navigate to new states using '#' anchors now work correctly. Shadow monitors the Address Bar in Chrome, and sends updates to Shadow devices as they happen.
  • Amazon Kindle Fire support — Shadow is available in the Amazon Appstore for Android, and will be installed easily on Kindle Fire devices.

Remark: As you may notice, the Windows Phone isn’t supported(yet).

How does it work?

After installing the Adobe Shadow app on your mobile devices and on your local machine, you can browse to a web page on your laptop/desktop browser and have it automatically pushed to all of your devices without actually touching the device. The only caveat is that all your devices should be connected to the same (WiFi) network.

For the detailed instructions, check out the following blog post: http://weblogs.asp.net/dwahlin/archive/2012/04/07/testing-mobile-websites-with-adobe-shadow.aspx

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cache stampede: when our cache turned against us

While investigating some performance issues, we ran into an ASP.NET Core API that cached a fairly expensive aggregation query for 60 seconds. Under normal load, that was fine: one request rebuilds the cache, everyone else reads from it. Under peak load, dozens of requests would arrive in that same expiry window, all see a cache miss, and all fire the same expensive query in parallel. The database didn't like that. That was the moment when our caching layer stopped helping and started hurting. A burst of requests comes in at the same time, all miss the cache, and all go hammer the database or the downstream API at once. That's a cache stampede . The cache was supposed to protect our backend, and for a few hundred milliseconds it did the opposite. Why this happens IMemoryCache.GetOrCreate (and its async sibling) looks like it protects you, but it doesn't add any locking on its own. Look at the naive version: public async Task<Report> GetReportAsync(string key) ...
Read more

A complex system designed from scratch never works

A few years ago, I worked as an architect on a big mainframe rewrite. I still count it as one of my failures. Not because the technology was wrong, but because I couldn't convince the management team to simplify the approach. Years later, the organization is still struggling to get the new system up and running. I left the project at the time, because I couldn't put my name behind an approach that would take very long and cost a lot of money without a working system to show for it along the way. Gall’s Law That memory keeps coming back to me, because it's a textbook case of Gall's Law playing out in real life. Gall's Law , from John Gall's Systemantics , states it plainly: A complex system that works is invariably found to have evolved from a simple system that worked. A complex system designed from scratch never works, and it cannot be patched to make it work. You have to start over with a simple system that works. What does that mean in practice,...
Read more