BoardVision: a specific identification workflow
BoardVision is the featured product, in development for iOS and Android. It reads memory chip markings from a photo or camera and compares them with reference data. The workflow connects the input image, reference match and result review for operators sorting desoldered memory chips.
The result has a defined scope. A matching reference does not establish that the chip works or determine its metal yield. Those limits are part of explaining the product, alongside what the app is intended to help someone do.
Margenta, VenKeep, Peptomy and Frame: products in development
Margenta is a web app that shows marketplace sellers the net profit left on each order. VenKeep is a web app that companies use to collect vendor documents such as insurance certificates, W-9s and licences and to track their expiry dates. Peptomy is a web reference on peptides and human anatomy for physicians and researchers; it gives no dosing or usage guidance. Frame explores visual tools for presenting digital products clearly. These descriptions communicate a direction, rather than a finished set of capabilities.
Detailed features, public availability and release dates are not announced here. Keeping that distinction visible lets readers understand the stage of each product without mistaking an exploration for a product they can already use.
Start the conversation with your task
If one of these directions relates to your work, describe the task you want to make easier. Tell us what starts it, which information you use and where the process becomes difficult to follow.
An example is often more helpful than a proposed feature. Explain what you do today and what a clearer result would allow you to decide. For uncertain inputs, describe how you check them before continuing.
Look for progress you can understand
A useful product explanation should show the problem, the workflow and the current stage. Screenshots can support it when they represent the actual interface. Claims should stay within what the product information establishes.
Our Products section and journal notes provide that starting point. Explore BoardVision’s workflow or contact ECHO with a concrete question about one of the directions. Clear questions help keep the discussion grounded in the work the product could support.