Swarmbot Device Wall: when to use View and when to use List

Use Swarmbot View for live screens, visual selection and synchronized control. Use List to check numbers, models, serials, LAN addresses, connection methods and sharing state. This guide shows how the two modes work together.

Use Swarmbot's View mode to see what your devices are doing now, and List mode to confirm exactly which device you are looking at. You do not have to choose one permanently. For a larger fleet, it is usually faster to identify the target in List, then return to View for visual monitoring and batch actions. The View/List switch sits beside the search field at the top of the Device Wall.

中文版本

Enterprise device-management products commonly combine a filterable inventory, stable identifiers, device details and remote actions. Microsoft's Intune documentation describes an All devices list with filtering and key columns, followed by per-device details such as model, OS and serial number. Read Microsoft's device-management overview Swarmbot adds a live visual wall because its users also need to answer a second question: not only “which device is this?” but “what is happening on its screen?”

Choose a mode in one minute

What you need to do Better starting point
Find a black screen, a stalled login or the wrong app View
Box-select devices, add with Ctrl, or use synchronized control View
Find a phone by number, model, serial or LAN address List
Check whether it uses USB, Wi-Fi, ACC or sharing List
Review group, online state, sharing state or expiry List
Open a control stream for one device Either mode

Stay in View when the screen itself answers your question. Switch to List when the question becomes “what model is this, how is it connected, and is it shared?”

View: see status, build a target set and act

View represents each device as a card with its live screen. The device number, connection badge and online state remain close to the picture. It is the right mode for:

  • watching where several phones are in a workflow;
  • selecting a group by clicking or drawing a selection box;
  • holding Ctrl while drawing another box so that earlier selections remain;
  • enabling Batch Sync so that one control window drives other selected devices;
  • double-clicking a card to open a stream, or using small-window control for quick work.

Dock Settings can add the model, serial number and LAN IP to each card; the business number always remains visible. Showing every field can make a small card crowded, so keep the screen clean for everyday monitoring and enable serial or IP only when inventory or troubleshooting requires them.

The size control at the top lets you shrink cards for an overview or enlarge them when you need more detail. For the selection and synchronized-control workflow, see the Swarmbot Device Wall selection and batch sync guide.

List: treat the fleet as an inventory you can verify

List compresses each device into one row. The current released version includes:

  • business number and remark;
  • model and Android or iOS version;
  • connection method;
  • LAN address;
  • hardware serial number;
  • online or authorization state;
  • Swarmbot's internal device ID;
  • group;
  • sharing state and expiry;
  • a Control button that opens the device stream.

These identifiers serve different jobs. The business number is the short label operators use every day. The serial number comes from the device and is suitable for matching a physical asset. The internal ID is the identifier used by Swarmbot APIs. A LAN address should not be treated as a permanent identity because it can change when the network changes.

If a LAN address or serial is unavailable, Swarmbot leaves it blank or shows a dash instead of presenting a port, URL or connection string as a hardware serial. Microsoft's device-detail documentation also notes that some hardware fields can be unavailable under particular platform conditions. A useful inventory therefore allows a missing value instead of inventing one. See Microsoft's device-detail reference

Select Control at the right of a row to open the stream. Double-clicking a row does the same. List is therefore not a dead report; it is an accurate way to find a device before acting on it.

Search and source filters come before either view

The search, group and source filters at the top of the Device Wall are the fastest way to reduce the working set. Source filters can narrow the page to USB, Wi-Fi, ACC, shared, remote, cloud or offline devices. When unauthorized devices exist, List can expose that state as a separate filter too.

A dependable workflow is:

  1. Narrow the fleet by source or group.
  2. Search for a number, remark or device detail.
  3. Use List to check serial, IP, connection and sharing state.
  4. Select Control for one device, or return to View to select a batch.
  5. Run app installation, media import, automation or another batch task.

This reduces mistakes when several phones share the same model and wallpaper. A similar-looking screen is not a reliable identity.

Three common examples

Verify targets before a batch installation

Use List to check the group, connection method, model and online state. Then return to View—or use the Dock—to select the current filtered scope. After starting the installation, use Recent Tasks for per-device progress rather than resending the whole batch when one phone fails.

A device has a picture, but you cannot identify the physical phone

Note the business number in View, then inspect its serial and LAN address in List. Match those values with the label on the phone or your network records. If the route is online but the screen, stream or controls fail, run Swarmbot Diagnostics from the device's context menu.

Check which devices are currently shared

Choose the Shared source filter. List shows the sharing state and expiry, and its Control button opens the device. For the owner, recipient and connection requirements, read the Swarmbot device-sharing guide.

The useful habit: identify in List, act in View

View and List are not separate fleets or independent workspaces. They are two ways to inspect the same devices:

  • List provides accuracy: identity, filters, connection and sharing details.
  • View provides context: live screens, target selection, synchronized action and visual control.
  • The stream window provides depth: input, installation, file work, automation and troubleshooting for one device.

View alone is often enough for a few phones. As the fleet grows, “verify in List, then act in View” is more dependable than searching through dozens of similar screens every time.

参考来源