Differences between "Browser" and "Native Browser" in akaBot Studio

When Studio was first released, it provided "Browser" activities. However, starting from version 2.1.1.1, a new category of activities called "Native Browser" was added.

Both sets of activities share many similarities, but there are key differences that are important to highlight.

"Native Browser" activities can accomplish tasks that were not possible with "Browser" activities, and they can also lead to shorter processing times in some cases. Unless you have specific needs, such as a requirement to support "Internet Explorer," it is recommended to use "Native Browser" going forward.

Point 1: Differences in Activities

The activities available in "Browser" and "Native Browser" are slightly different.

• Activities in "Browser" but not in "Native Browser":
  • Launch Attached Browser (B)
  • Browser Scope (B)
  • Send Shortcut Keys (B)
  • Extract Data (B)
  • Wait Until Element Exists (B)
  • Handle Alert (B)
• Activities in "Native Browser" but not in "Browser":
  • Get Element (NB)

Point 2: Supported Browsers

Another difference between the "Browser" and "Native Browser" activities is the browsers they support. The supported browsers for each are shown in the table below.

Note: Internet Explorer has a dedicated category named "Internet Explorer".

Point 3: Browser Launching
In "Native Browser" activities, if a site that has already been logged into is launched, there is no need to re-enter the ID and password, and the login state is maintained.

For example, when using the "Browser" activity to handle login processes, you need to create a workflow that uses "Type Into (B)" and "Click (B)" activities to enter the ID and password. However, with "Native Browser" activities, if the site is already logged in with the correct ID, these steps can be skipped. Below is an example of a workflow for reference.

Note: In actual operation, considerations must be made for scenarios such as "If the logged-in ID is different" or "If the session has expired and automatic logout has occurred," so please create a workflow that suits practical use.

Note: Many sites require reCAPTCHA verification or prohibit robotic operations. Please carefully check the site's terms and conditions.

Example of a workflow using "Browser" activities:

Example of a workflow using "Native Browser" activities (assuming the login state is maintained):

Note: The images provided are examples. The actual workflow may differ depending on the site.

Below is a comparison table showing the execution time for a workflow that displays the top page of akaBot Portal and then navigates to "Account" > "Inquiry History" after logging in. Please note that the results may vary depending on the PC's specifications and network environment, so treat this as a reference only.

Execution Time Comparison

This test assumes that the workflow was executed with the correct ID already logged in. Please create and operate workflows that are aligned with practical use.

Point 4: Private Mode
The "Native Browser" activity allows the use of "Private Mode" through a property setting. For more details on "Private Mode," refer to the description in "Open Browser (NB)."

Point 5: Support for the Latest Version of Chrome
Due to the difference in update frequencies between Chrome and akaBot Studio, there may be cases where the version of Chrome you are using is not included in the selection list.

For "Browser," you need to follow the steps in the "How to Add Chrome Version to akBot Studio" to resolve this issue. However, in "Native Browser," you can use Chrome without being concerned about ChromeDriver, so the above workaround is unnecessary.

Point 6: Waiting Time Before and After Activity Execution
"Native Browser" activities include properties for "Wait Time After Execution" and "Wait Time Before Execution" by default. (These properties are not included in some activities, such as "Open Browser (NB)").

When using "Browser" activities, some users might have inserted a "Wait" activity between activities (such as between "Click (B)" and "Click (B)") when screen transitions didn't proceed smoothly. With "Native Browser," the waiting time can be set without inserting a "Wait" activity, keeping the workflow simple.