How to build a Mobile Scenario using “Play&Record” feature of the Scenario Studio (Mobile)

This article includes following contents,

Section 1: The scenario you will make

Section 2: What you need to prepare before you start

Section 3: How to start building a new scenario

Section 4: Using [Play&Record] feature

Section 5: Testing the scenario


Section 1: In this tutorial, you will make the following scenario

1) Start a Calculator app

2) Input numbers and operands

3) Execute calculation and see result


Section 2: What you need to prepare before you start

1) Download and install Scenario Studio to your PC?

2) Download and install ARGOS UX Robot (Android or iOS) to your phone?

*) Please make sure that the PC and the phone are set up correctly according the ARGOS UX Robot set up manuals and connected together via USB cable.

3) Your phone must have a Calculator app installed and the icon is showing on the screen now.


Section 3: How to start building a new scenario

1) Start Mobile Scenario Studio and then click [New].

2) When [CreateScenario] window opens, give the new scenario a name and register ARGOS UX Robots and Company under which your scenario will be built.  (You can change name and registration at any time later.)


Section 4: Now try the [Run&Record] feature

*) No Run&Record feature available for Android as there is a known bug. Projected fix release in December 2017

1) In the main menu click [Tool] and then [Record].

2) Choose an ARGOS UX Robot from the [Device List] window.
*) if you only have one UX Robot assigned to the scenario it is automatically selected.

3) Open VNC Viewer, enter password and show the screen of the ARGOS UX Robot.









4) In the [Auto Recorder] window select [Select Vnc Window] and click.

5) From the [VNCWindowList] choose an UX Robot with which you record the scenario movements and go back to [Auto Recorder]window and confirm the [Record] button is active.


6) Click on [Record] will start the recording and click again will stop.

7) From the VNC screen, start the Calculator app.
Please note that manipulating the phone screen directly will NOT record scenario.


8) In this expample, tap the buttons 5, 0, 0, +, 5, 0, 0, and = in sequence.

9) The screen should show the result of calculation.

10) Now stop recording by clicking on [Stop Record].

11) Wait until the [Complete] bar shows at the bottom of the [Auto Recorder] window.


Section 5: How to test your scenario

1) Go to [Run] page on the Scenario Studio and click on [Run Test].

2) The UX Robot phone that is connected to the Scenario Studio PC should run the scenario automatically.

3) If the scenario runs successfully, the measured performance data shall be uploaded to the server and the screen should show [Uploading] message. (The [Show Result] button is not functional with the current version.)




Shige Sato


Raising your conversion rate by using Google Analytics and ARGOS UX Robot.

All the businesses which promote and advertise online should be interested in having their visitors stay longer in their online stores and sell them more products or services.

Often flash sales and event promotion become marketing tools.

And it would be inefficient if the companies choose to increase equipment before they have a right prediction of the number of visitors.

However, you can ensure adequate service performance by giving the total performance of the service or estimating visitors.  And you can also get assisted by the CDN (Contents Delivery Network) services when there are exceeded numbers of visitors momentarily over the capability. Google Analytics is easy to use tool especially to analyze the behavior of the visitors.


Google Analytics

For better use of GA, it is necessary to analyze Bounce Rate and Conversion Rate in depth from the basic analysis reports.

‘Landing Page’ is the first page that a visitor sees on the Website or App screen, and  ‘Exit Page’ is the last page where the visitor saw when the switch to another Website or App.

And the definition of bounce rate in GA is as follow.


 In Analytics, a bounce is calculated specifically as a session that triggers only a single request to the Analytics server, such as when a user opens a single page on your site and then exits without triggering any other requests to the Analytics server during that session.



There are a number of reasons your website can have a high bounce rate.

  • No contents what they want to know
  • No reason to browse more deeply (or no more fascinating contents)
  • Tired to wait for a slow loading
  • It’s enough.


There are more of analysis reports for it to identify the cause easier.

For example, ‘Page Speed’ is a good report on slow pages.

What would you do if you identify the page with a high bounce rate becomes slow?

For your reference, GA measures data from the visitor’s devices.

That is, the slow page speed implies the slow response time of the Web or App server measured from the visitor’s device.

The response time of the Web or App server is determined by the service time which is constituted by the Web/App server, WAS, Network, DB, etc.

Conversion Rate’ report is also one of the major reports.  When you set the goal page or screen, it shows the number of visitors who visited your goal pages on a total number of visitors.

In another word, increased conversion rate means that the site is leading visitors to the target page and also to perform the desired action on pages such as service subscription, purchase order, sign up, etc.

Of course the lower the Conversion Rate, the higher the Bounce Rate.

The difference between two is that Bounce Rate targets the entire pages or screens and Conversion Rate targets a specific target page or screen.

The reason for the lower Conversion Rate is related to the reason for higher Bounce Rate.

Unfortunately, GA cannot provide you any information in this regard.


Fig. GA Landing & Exit page sample


Analytics using ARGOS UX Robot


ARGOS UX Robot also measures from the visitor’s point of view. However, there is a significant difference from GA.

ARGOS UX Robot collects and analyzes each page or components constituting the page or screen; network speed, server response time, download traffic speed and page size and more.

ARGOS UX Robot distinguishes the issue of each component: whether it has slow response time; if the issue comes from network or server; whether the component is an external site or internal site.

Also, ARGOS UX Robot measures the CPU and memory usage of the device to analyze whether the device is performing poorly, and whether the performance of the system is enough to run the service Web or Apps.

This feature helps visitor’s burden on their devices.



GA does not perform enough on processing information for mobile apps, ARGOS UX Robot has solved those problems with additional features for mobile app analysis.

Your conversion rate will increase by using ARGOS UX Robot Analytics with GA Analytic.


Please contact us for more details.


Seongho Jang
R&D Director, ARGOS LABS

UX Robot for Web/App performance analysis

The Internet has been growing at unprecedented rates, led to an upsurge in research, development, and investment in web service. There are reasonable arguments that it will continue to grow at this pace for the rest of this decade.  Enterprises around the world planted their powerful websites to introduce their businesses and to perform their e-commerce.

Ever since Kbytes era, the speed has been the critical factor for the clients to give solid understanding to the company. IT industry has been creating a solution to measure, analyze and improve Web services because they understand that how speed affects the bottom line of businesses.

UX Robot for PC

The accurate evaluation of Web service quality starts from downloading individual components from a Web HTML documents like index.html and then measuring the time of constructing the final screen.  Currently, most of the browsers support this feature. However, in case of internet shopping malls, streaming services like Spotify, Netflix and internet banking services which are protected by security software, it is not possible to measure performance. They need another solution. UX Robot for PC provides a Packet analytics as well as a streaming MOS analytics. It measures the same as user’s web browsing activity, because it uses a real web browser, not the browser emulation.


UX Robot for Mobile

Since Smartphones set to become the fastest spreading technology, it brings together the quality management and the app performance analytics. There are two types of the smartphone applications: A hybrid app is a mobile app that contains a web view to run a web application inside of a native app vs. Native apps are written in a programming language specific to the platform they’re being developed for. There is a definite distinction in measuring technology between the native and the hybrid way of development.


Figure. e-Bay scenario run by UX Robot for Mobile


With Scenario Studio and UX Robot for Mobile,

you can record and save a user’s touch gestures and individual screens to construct the usage patterns in it. And it allows you to measure and perform analytics for both hybrid apps and native apps.   UX Robot for Mobile and its Scenario Studio has a top rated accuracy, and you can also use same scenarios in different smartphone devices.

UX Robot for Mobile provides the same level of additional analytics based on Packet so that you can apply to the broader range of services.



Today’s “Web / App performance measurement” methods are changing. We must define user’s action flow first and then measure the web/app performance accordingly.
UX Robot can reproduce same user’s action like user’s shopping process on the internet. With Scenario Studio, you can easily and quickly create scenarios suitable for your service and monitor 24/7 using the UX Robot from anywhere in the US.


Seongho Jang
R&D Director, ARGOS LABS


The Forth Industrial Revolution

As it is stated in in the meaning of the fourth industrial revolution following the flow of thinking, the keyword of forth industrial revolution (IR) is automation; the first IR was steam; the second IR was electricity; the third IR was communication.

Automation is known as the robotic manufacturing system, but now it needs more attention in the software industry.

The software industry is taking the initiative over hardware along with the transition from third industry to the fourth.


  • GE announces its transition to the software and analytics company in 2017.
  • IBM has already transformed itself from a hardware company to the software and service company from the 2000s.


Ironically, the software industry is less automated than hardware industry regardless of industrial transition.

In the process of a software development project, developers must intervene from every procedure to the test results, and involve in the release, deployment, and operation process.

Now we can infer the direction to win the competitiveness in the fourth IR, which is the automation of development and operation system.

Next table shows the transition of Industrial Revolution.







CoalPetroleumElectricityRenewable Energy

IoT (Internet of Things)


RailwayAutomobileSmartReplicator (Local Production)
InfluenceConsumer Goods and Light IndustryElectrochemistry, Heavy Chemical IndustryIT

Every Industry


MachineMass ProductionDigital

AI (Artificial Intelligence)




Factory system and mechanization
by steam engine
Mass production by standardization of work and division of laborAutomation revolution by industrial robots

Automation with AI
(Artificial Intelligence)
Low volume and multi-product production


This paradigm emphasizes that only companies will survive who meet the diverse needs of customers by shifting its traditional manufacturing methods to automated small volume production. So, every enterprise must meet digital transformation to change and make a revolution in their business model. In regards of software digital transformation include the change of architectures.


  • Today’s demands are simply not met by yesterday’s software architectures. from
  • Mobile generation requires different development methods and architectures.


Software companies have out-competed traditional firms and even acquire hardware companies.

You can compare the top five companies with the highest market cap in 2007 and 2017.






Google Alphabet


4China Mobile


(Industrial and Commercial Bank of China)



Digital conversion is the way to ride on the changing paradigm, and companies are more likely to disappear without it.


DevOps is one of the most critical factors in the software-based digital transformation.

DevOps is an enterprise software development methodology used to unify an agile relationship between Development and IT Operations.


Let’s take a look at the DevOps of the Unicorn Company to see how they change and improve the relationship by advocating better communication and collaboration between the two business units.


Unicorn Company and DevOps



  • Continuous iterations and incremental development
  • Facebook developers work in independent and released small changes frequently.
  • Done is better than perfect.
  • Code wins arguments.
  • The best idea and implementation should always win. 


Google (Ten Things we know To Be True in Google)

  • Focus on the user and all else will follow
  • It’s best to do one thing really, really well.
  • Fast is better than slow.
  • Democracy on the web works.
  • You don’t need to be on your desk to need an answer.
  • You can make money without doing evil.
  • There is always more information out there.
  • The need for information crosses all borders.
  • You can be serious without a suit.
  • Great just isn’t good enough.



  • High Availability, but move fast.
  • Tools encourage best practice, but freedom to do the right thing.


Amazon Leadership Principles

  • Moving Fast


So, Big Unicorns’ common goals,

  • Moving Fast
  • Focus on customers


Goal of DevOps


DevOps is not about a technology, DevOps is about a business problem.

 As above, unicorn companies have been applying DevOps methodology to respond customers’ needs in this fast moving business environment.


Steps of DevOps


Understanding the business value of DevOps is must do, but how about the implementation?  As to the steps of DevOps, the below will help you to approach your DevOps implementation; these can be boiled down to eight steps.


At first, there are four developmental steps as below.





1PlanUnderstand the problems and plan the solutions.No

Men use tools as aids to capture requests.


CodeCode software based on step 1.NoCoding by men varies productivity.
3BuildComplete step 2 coding to the degree of an executable implementation.Yes

Automation by CI/CD tools.


TestTest whether the completed implementation of the step 3 is running as planned.No
(Mostly No)

Partial automation is possible for the unit tests, API tests, and UI tests.


And the below are four operation steps.

As I said before, every company which apply DevOps make their efforts on how to minimize human intervention and automate above 8 steps.



ReleaseFix step 4 with the release.YesPrepare and generate the release through collaboration with the version control systems.
6DeployPrepare the deployment and service of step 5 depending on the operating system environment.Yes

Implement automation through a container or an orchestration tool.



Operation of the deployed service from step 6.


The goal is to operate automated processes with minimum human involvement.


Monitor service operation from step 7.

(Mostly No)

Identify anomalies of the system through monitoring log and event by human intuition and analytics.


Measuring DevOps and IT Performances

Next table shows how the unicorn companies go fast and do their own DevOps cycles forever. The faster cycle tends to be more fast product refinements and prompt user response.


  • Deploy frequency (Note: NOT delivery)
  • Mean Time to Recover (MTTR)
  • Lead Time for Changes



Deploy FrequencyDeploy Lead TimeReliabilityCustomer Responsiveness
Amazon23,000 / dayMinutesHigh



1 / dayHoursHighHigh
Google5,500 / dayMinutesHigh



500 / dayMinutesHighHigh
Twitter3 / weekHoursHigh


Typical enterprise

Once every 9 months

Months or quartersLow / Medium

Low / Medium

From a book, The Phoenix Project (2013)


The above chart shows that many companies run the DevOps cycle at least once a day, and the more the cycle they run, the more competitiveness they take.



Let’s take a look together with the automation, a keyword of the Forth Industrial Revolution and DevOps.


The needs for automation

To gain competitive advantage, what can be the best way to run the cycle faster?  The answer is automation.


Obstacles of Automation

Ideally, the fastest cycle performs from the complete automation especially in the fourth developmental step and the eighth operational step.  The trick is to strike a point of minimum human intervene and the maximum automation on development, testing, and deployment.




StepContentsAutomationHow to automate



PlanUnderstand the problems and plan solution method.No

Increase automated problem detection using AI.

2DevelopmentCodeCode software based on step 1.No

There is no complete automation in coding, but it is now an issue in AI field.


DevelopmentBuildExecute and implement coding from step 2.Yes
4DevelopmentTestTest the implementation of step 3.No
(Mostly No)

Check the error points.


OperationReleaseFix the release of step 4.Yes
6OperationDeployPrepare the deployment and service of step 5 to meet each operational environment.Yes


OperateRun the deployed service.Yes/NoIs the current service running normally?
8OperationMonitorMonitor various statuses while running the service of step 7.No
(Mostly No)

Is there any problem with the network, system, resources, etc.?



The key to the lead of competitiveness remains whether the resolution made it through automated testing, automated operations, and automated monitoring.

Most APM products need to insert some code at step 2 (code) and wait at step 7 (operate) and get the result at step 8 (monitor).


What ARGOS can do! 


ARGOS can make a difference in step 8.



Step           ContentAutomationWhat ARGOS can do
1DevelopmentPlanUnderstand the problems and plan solution.No


DevelopmentCodeCode software based on step 1.No
3DevelopmentBuildTest the implementation of step 3.Yes


DevelopmentTestTest the implementation of step 3.No
(Mostly No)
ARGOS can automate UI scenarios and report the anomalies.
5OperationReleaseFix the release of step 4.Yes



DeployPrepare the deployment and service of step 5 to meet each operational environment.Yes
7OperationOperateRun the deployed service.Yes/No

ARGOS can run the service from the user perspective for a web or app, and analyze anomalies.


OperationMonitorMonitor various statuses while running the service of step 7.No
(Mostly No)

ARGOS specializes its service in GA or APM industry by providing the analytics based on the real user action while existing APM services are focusing just on monitoring service.


Argos can automate step 4 and 7 to reduce the number of cycles and the cycle time without any code level modification.


Jerry Chae


Application performance solutions like ARGOS Service provide a variety of measurement metrics: availability, response time, CPU usage and so on.

However, those metrics do not satisfy visibility and applicability of indicator values.

ARGOS now presents ARGOS SCORE to show key metrics at a glance so that you can detect directly affected performance issues among the various measurement indicators.

ARGOS SCORE can quantify and manage the performance quality of the online services as a single value.

Performance management of online service is one of the critical factors for business management, and ARGOS SCORE enables easy comparison with competitors to lead to a competitive edge.

ARGOS SCORE measures the key metrics: Availability, Response Time, Variation Rate, Page Size, and Number of Requests, using the weighted average because each one has different degrees of impact on performance quality..



The availability is a measurement metrics to see if the user can access the Web or mobile app service.

The highest level of online service requires triple 9 (99.9%), and it means 8.76 or fewer hours of service failure per year.



Response Time

The response time is the speed of the Web or mobile app service that the user experience: time from the start of loading to the completion.

Response time should not exceed three seconds because the maximum endurance time of the end-user in the online services is 3 seconds before leaving to a competitive service.



Response Time Variation Rate

The response time calculates an average value of measurements over a certain period.  But this average value does not reflect the actual response time when the variation of the sizes is significant.

In the figure, the average response time of service A and B shows both 2 seconds in 24 hours.  However, in case of service B, the response time of service has to be 3 seconds because the response time of most high traffic hours, 10-18 o’clock, hits 3 seconds.

It is essential to keep the average response time low for a fast user experience rate, but it is also important to maintain the response times constant without large variations.

ARGOS uses the standard deviation to calculate the response time variation rate.


Page Size

The page size is the byte count when a device is loading a web or mobile app page.

A larger page requires longer download time, and it can directly effect on end-user response time.

An inefficient large page size creates more costs not only for a service provider, and downloading a large page size in a mobile environment causes not just a delay in response time to the user but also an additional communication cost burden.

Most online services use CDN service, so a large page size incurs additional CDN cost for the service provider.  It is cost effective to manage page size within 1MB for the PC environment and 500KB for the mobile environment.


Number of Requests

The number of requests is the count of HTTP requests from the device to the server while it is loading the web or mobile application page. It is the number of components such as image, HTML, CSS, JavaScript, etc.

Excessive requests to the server result in response time delays, so you should limit the number of requests using CSS Sprites within 100 in the PC environment and 50 in the mobile environment.



The following figure is an example of ARGOS SCORE; it measured online shopping websites for Amazon and eBay.

The performance quality of eBay is 93.17, which exceeds Amazon’s 86.17.

ARGOS SCORE shows a radar chart to see the weak point at a glance and compare with a competitor.

In the example, Amazon’s page size and requests metrics are significantly lower than eBay, and you can read that Amazon’s page size is 5.94 MB and requests are 238, which is more than twice from eBay.  It is clear that Amazon needs to optimize the page size and number of requests according to ARGOS SCORE.



  • ARGOS SCORE’s key metrics gives a direct impact on performance.
  • ARGOS SCORE shows the performance quality at a glance.
  • ARGOS SCORE’s competitive management ensures continuity of online business.


Young Kim