Seeing

I approached Seeing as a practical tool rather than a flashy gadget companion. Developed by Lonsen Electronics Limited, it is designed to let you talk with and see visitors from a smartphone. That simple purpose makes it potentially useful for everyday home access, but it also means the quality of the experience depends heavily on setup, connection conditions, and how well the app fits the visitor device you already use.

My overall impression is that Seeing makes the most sense for someone who wants a phone-based way to respond to visitors without being tied to a traditional indoor monitor. It is free to install, aimed at Everyone, and available on devices running Android 6.0 or newer. The current version is 2.0.8, and its average rating of 4.4 from around 25 thousand ratings suggests that many people find the basic idea worthwhile.

Still, I would not treat it as a universal replacement for every door-entry arrangement. The app is most valuable when the compatible visitor hardware is already installed and the phone has a reliable connection. If either side is poorly configured, the first reaction may be to blame the app, even when the real problem is the network, phone settings, or the device at the entrance.

Where the experience usually gets stuck

The first call is not always the real test

The most confusing part of an app like this is that several separate things must work together. Seeing has to be installed on a compatible phone, the visitor-side device has to be active, the account or connection process has to be completed correctly, and both ends need to communicate. A failure at any one point can look like the same symptom: no alert, no picture, or no usable conversation.

I would begin by separating those symptoms. If the phone never reacts when someone visits, the issue is probably related to notifications, background operation, connection status, or pairing. If the phone rings but the image is missing, the problem may be the visitor device, camera connection, or network path. If video appears but speech is unreliable, microphone access, speaker volume, Bluetooth routing, or bandwidth deserves attention before reinstalling anything.

This distinction saves time. Reinstalling an app can clear a damaged local state, but it will not repair a disconnected entrance device or a phone that blocks alerts. Seeing is a communication tool, so troubleshooting it like a normal offline utility is usually the wrong approach.

Notifications are part of the core function

For this type of tool, an alert that arrives late is almost as inconvenient as an alert that never arrives. I would check whether notifications are enabled for Seeing and whether the phone is using a mode that silences incoming alerts. Battery-saving settings can also interfere with apps that need to remain ready in the background, especially on phones that aggressively limit background activity.

There is a useful practical habit here: test the app while the phone is in the same everyday state in which you expect to use it. A test with the app open does not prove that an alert will appear when the phone is locked, sitting in another room, or connected to a different network. I would test those situations separately and note whether the failure is consistent or occasional.

If alerts work only while Seeing is open, that points toward phone-level restrictions rather than a problem with the visitor interaction itself. If alerts never appear even with the app open, I would move attention to the connection between the visitor-side equipment and the app.

Video and audio can fail independently

Seeing is meant to combine seeing and talking, but those two parts should be judged separately. A clear image does not guarantee that the microphone path is available, and hearing a visitor does not prove that the visitor can hear you. I recommend making a short test call and checking both directions deliberately instead of asking only whether the screen opened.

On the phone, confirm that the volume is high enough and that sound is not being redirected to headphones, a car system, or another Bluetooth accessory. During a call, look for the normal microphone control and make sure it has not been muted. These are simple checks, but they explain many apparently random audio complaints.

For video, check whether the picture is consistently blank or merely slow to appear. A delayed image can indicate a weak connection, while a permanently missing image may indicate a problem on the visitor-device side. I would avoid drawing a conclusion from one test made in poor signal conditions.

Permissions deserve a calm, deliberate check

When an app needs to support communication, the phone may ask for access related to notifications, microphone use, or other functions required by the operating system. I would read each request in context and allow only what is needed for the features I intend to use. If a permission was denied during setup, the app may not explain the consequence clearly enough, so revisiting the phone’s app settings can be worthwhile.

At the same time, I would not grant permissions simply because a prompt appears. The useful approach is to connect each permission to a visible task: speaking requires microphone access, while timely incoming communication depends on notification behavior. If a permission does not relate to the function being tested, I would leave it disabled until the app clearly requires it.

Setup checks that prevent avoidable trouble

Prepare the phone before pairing

Before starting, I would update the phone’s operating system as far as the device supports, make sure there is enough free storage for normal app operation, and close any aggressive cleaner or task-killing utility. Seeing supports Android 6.0 and later, but compatibility on paper does not guarantee identical behavior across every phone manufacturer’s software.

I would also decide which phone should receive visitor calls first. Using several phones can be convenient, but adding devices before the first connection is stable makes it harder to identify which one is failing. My preferred order is simple: establish one working phone, test it while locked, and only then consider expanding the arrangement if the available setup supports that.

Another useful check is the phone’s date and time. Incorrect system time can cause confusing connection behavior in some internet-based services. It is not the first thing I would change, but it is quick to verify and avoids chasing a problem caused by the phone’s basic configuration.

Use a controlled first test

I would not make the first test during an important delivery or while someone is waiting outside. Instead, arrange a quiet test with another person who can stand at the visitor device and describe exactly what happens. Ask them to test the call, image, and two-way audio independently.

Write down the sequence rather than relying on memory. For example, note whether the entrance device reacts, whether the phone receives an alert, how long the image takes to appear, and whether each person can hear the other. This small record is much more useful than saying that the app “doesn’t work,” because it identifies the stage where the communication chain breaks.

Testing from the location where the phone is normally kept is especially important. A phone that works beside the router may behave differently in a bedroom, hallway, basement, or office. Seeing is intended for real visitors, not just laboratory conditions, so the practical test should resemble the real routine.

Keep the connection path in mind

Because the app connects a smartphone with a visitor-facing device, network stability matters on both ends. I would test the phone on its usual Wi-Fi and, where appropriate, through its mobile connection. If one works and the other does not, that comparison provides a valuable clue without requiring technical tools.

Restarting the phone and the relevant visitor equipment can also clear a temporary connection state. I would power-cycle only the equipment I understand and avoid changing several settings at once. If the problem disappears after a restart, I would still repeat the test later; a one-time recovery does not prove that the underlying setup is stable.

For households with multiple network names, extenders, or frequently changing connections, consistency is helpful. The phone should not be silently switching between a weak signal and a stronger one during a visitor call. Keeping the phone in a location with dependable reception is often more effective than repeatedly reinstalling the app.

Understand the cost boundary

Seeing is free to download and use as an app, but it includes in-app purchases priced from $19.99 to $99.99 per item. I would therefore check the purchase screen carefully before confirming anything and make sure I understand whether a paid item is relevant to my particular setup. The free installation is not the same thing as every possible function being free.

This matters most for someone comparing Seeing with a basic doorbell or a simple intercom. The right comparison is not just the download price; it is the total cost of the visitor hardware, any optional app-related purchase, and the effort required to keep the system working. A free app can still be the sensible choice when the compatible equipment is already present, while a different solution may be cheaper for someone starting from nothing.

Keep expectations realistic on older phones

The minimum operating-system requirement is Android 6.0, which gives the app a broad compatibility range. Even so, an older phone may have limited background behavior, slower video handling, or manufacturer-specific restrictions. I would not judge the app solely by how it behaves on an aging spare phone if a newer device is available for the main household role.

On the other hand, a newer phone is not automatically better if its battery controls are unusually aggressive. The practical question is whether the chosen phone can reliably receive alerts and maintain a conversation in its normal locked-screen state. That is more important than having the latest hardware.

Recovering the workflow when something breaks

Start with the least disruptive fix

When Seeing stops responding, I would begin with the current connection and notification state rather than deleting everything. Open the app, check whether it appears connected, and perform a controlled test. Then close and reopen it, restart the phone if needed, and repeat the same test. This preserves useful clues and avoids unnecessary setup work.

If the app is visibly stuck, clearing its temporary state through the phone’s normal app controls may help, but I would be careful with any option that removes stored information. Before using a reset or reinstall, I would make sure I know how the visitor connection is restored. Losing a local configuration during a rushed troubleshooting session can turn a small problem into a longer one.

Reinstalling is most reasonable when the app fails in a repeatable way after ordinary restarts, or when a recent update appears to have left the local installation in an unusable state. After reinstalling, I would repeat the setup slowly and test one function at a time instead of assuming the entire system is fixed.

Recover from a failed pairing attempt

A failed pairing process can leave the phone looking almost ready while the visitor device remains unlinked. I would avoid starting repeated pairing attempts immediately. First, close the app, restart the phone, and check whether the visitor equipment is powered and available. Then begin one fresh attempt with both devices nearby if the setup allows that.

It is also worth checking whether the phone is connected to the intended network and whether another household member has already changed the visitor device’s configuration. In shared homes, a previous setup attempt can be the hidden reason a new phone cannot complete the process. The best recovery is to establish which phone or account is currently treated as the active connection before making further changes.

If pairing succeeds but the first visitor call fails, I would treat those as separate stages. A completed setup does not necessarily prove that notifications, audio, and video are all functioning. Testing each part gives a clearer recovery path.

Handle intermittent calls differently from total failure

An app that never connects and an app that works four times out of five require different thinking. Total failure points toward setup, permissions, power, or a missing connection. Intermittent failure points more strongly toward signal quality, background restrictions, congestion, or an unstable visitor device.

For intermittent problems, I would record when failures happen. Do they occur only when the phone is locked, only on mobile data, or only when someone is already using the home network heavily? A pattern can reveal the cause without advanced diagnostics. I would then change one condition at a time and repeat the test.

This is also where expectations matter. A phone-based visitor system is convenient, but it is not the same as a dedicated indoor monitor with a fixed connection and constant power. If missing one visitor is unacceptable, I would consider whether Seeing should be a convenience layer rather than the only way to know someone is at the door.

Know when to stop resetting

Repeatedly resetting the app, phone, and visitor equipment can create more confusion than it solves. Once I have confirmed that the same failure survives a restart, a notification check, and a controlled network comparison, I would stop making random changes. At that point, the most useful next step is to identify whether the issue belongs to the phone, the network, or the entrance device.

That approach also makes support conversations more productive. Instead of reporting only that Seeing is broken, describe the exact stage that fails: no notification, delayed image, one-way audio, or unsuccessful pairing. Include whether the failure occurs on Wi-Fi, mobile data, a locked phone, or an open app. Clear observations are more valuable than a long list of attempted resets.

When the app is not the cause

The phone may be silencing the experience

Modern phones often manage battery, notifications, and background activity differently. If Seeing works while open but not when the phone is idle, I would inspect those system controls first. Do not assume that a quiet phone means the visitor device failed; the alert may have been filtered before it reached the screen.

Sound settings can create a similar illusion. A phone may display an incoming event without making an audible alert, or it may route the conversation through an accessory that is not nearby. Testing with accessories disconnected and the phone’s normal speaker active helps isolate that kind of confusion.

Screen-lock behavior is another useful dividing line. If the conversation works only after manually opening the app, the issue is likely in notification or background handling. If the app opens but the call itself cannot establish, the connection path deserves more attention.

The home network may be the weak link

Video communication is more demanding than sending a text message. A network can appear fine for browsing while struggling with a live visitor conversation. If the image freezes, speech breaks up, or calls fail during busy periods, compare the experience at a quieter time and from a different connection where possible.

I would also consider the physical position of the visitor device. A camera or intercom at the edge of wireless coverage can produce symptoms that look like an app defect. If the entrance is far from the router or separated by thick walls, the phone may be perfectly healthy while the visitor device has an unreliable path.

When only one phone has trouble, compare it with another compatible phone before changing the whole network. When every phone has trouble at the same time, the shared visitor device or network becomes the more likely focus. This simple comparison is one of the most useful ways to avoid blaming the wrong component.

The entrance equipment remains part of the system

Seeing cannot compensate for a visitor device that is unpowered, disconnected, muted, or unable to provide a usable image. I would check the entrance side carefully and ask whether its indicator, screen, or call action behaves normally. If the visitor device does not initiate the event, the phone app may never receive anything to display.

Physical conditions can matter too. A blocked camera view, unusual lighting, or a covered microphone can make the app appear to have poor video or audio even when the connection is functioning. These are easy details to overlook because the phone is the part most visible to the user.

Choose another option when reliability matters more than mobility

I like the freedom of answering from a smartphone, but some homes are better served by a dedicated indoor monitor, a conventional intercom, or a more complete smart-door system. Those alternatives may be preferable when several residents need predictable access, when visitors must be handled during weak phone coverage, or when the household does not want to depend on background notifications.

Seeing is a better fit when smartphone access is the main attraction and the existing visitor equipment already suits the household. It is less compelling if I need a complete hardware package, a guaranteed always-on display, or a system that is simple for people who do not want to manage phone permissions and connection settings.

My practical verdict after using it

Who will get the most from Seeing

I would recommend Seeing to someone who wants to answer visitors from a phone and is comfortable doing a careful first setup. It can be particularly useful for people who are not always beside an indoor intercom, provided the phone can receive alerts reliably and the visitor-side equipment is compatible with the workflow.

The app’s strongest quality is its directness. It focuses on the useful moment: a visitor arrives, the phone provides a way to see what is happening, and conversation can take place without requiring the user to remain beside a fixed station. That is a meaningful convenience in a home where the phone is already the device people carry.

The app also has a reassuring level of adoption, with over 500 thousand installs and a 4.4 average. I would not treat those figures as proof that it will work perfectly on every phone, but they do indicate that this is more than an experimental tool with no established audience.

Who should think twice

I would hesitate to choose it as the only visitor alert for a household where missed calls create serious problems. The phone, operating system, network, and entrance equipment all have to cooperate. That flexibility is convenient, but it introduces more possible points of failure than a dedicated wired solution.

I would also think twice if I am shopping for a complete system rather than adding smartphone access to equipment I already own. The possible in-app purchases, together with the cost of compatible hardware, mean that “free” should not be the only part of the buying decision. Compare the complete setup with a dedicated alternative before committing.

What I would do before relying on it daily

I would install it on the phone that will actually be carried, complete the setup without rushing, and test a visitor call while the screen is locked. Then I would test two-way audio, video appearance, Wi-Fi behavior, and mobile connectivity separately. Finally, I would repeat the test at the entrance and at the place where the phone normally sits.

I would keep a short troubleshooting note with the successful conditions: which phone receives the alert, which connection works best, and whether any accessory affects audio. That may sound excessive for a small tool, but it makes recovery much easier after a phone update, router change, or accidental permission adjustment.

Final assessment

Seeing is a focused Tools app from Lonsen Electronics Limited that can make visitor communication more flexible by moving the interaction to a smartphone. I find the idea useful and practical, especially when the compatible entrance equipment is already in place. The free app and Everyone age rating also make it approachable for ordinary household use, while support for Android 6.0 and newer keeps the potential device range broad.

My recommendation comes with one condition: treat setup and phone behavior as part of the product, not as afterthoughts. Check notifications, test the locked-screen workflow, separate audio from video problems, and compare Wi-Fi with mobile connectivity before deciding that the app is unreliable. The best reason to use Seeing is mobility; the main trade-off is dependence on a complete, well-configured communication chain.

For my own shortlist, I would place it above a basic alternative when answering visitors from different rooms is the priority. I would choose a dedicated intercom or a more self-contained system when constant availability, shared household access, or simpler operation matters more than using a phone. In the right setup, Seeing is a useful bridge between the entrance and the device already in your hand, but it rewards a careful setup far more than a casual installation.

FAQ