<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Rihaan Hashmani</title>
    <description>The latest articles on DEV Community by Rihaan Hashmani (@rihaan_hashmani_3070e3d22).</description>
    <link>https://dev.to/rihaan_hashmani_3070e3d22</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209405%2F4c6786bf-2983-4074-9376-5aefa9750341.png</url>
      <title>DEV Community: Rihaan Hashmani</title>
      <link>https://dev.to/rihaan_hashmani_3070e3d22</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/rihaan_hashmani_3070e3d22"/>
    <language>en</language>
    <item>
      <title>Recall AI</title>
      <dc:creator>Rihaan Hashmani</dc:creator>
      <pubDate>Mon, 26 Oct 2026 19:10:12 +0000</pubDate>
      <link>https://dev.to/rihaan_hashmani_3070e3d22/recall-ai-1ncm</link>
      <guid>https://dev.to/rihaan_hashmani_3070e3d22/recall-ai-1ncm</guid>
      <description>&lt;p&gt;RecallAI: Building a Second Memory with Computer Vision at Cal Hacks 13.0&lt;/p&gt;

&lt;p&gt;This is a submission for the MLH x DEV Writing Challenge.&lt;/p&gt;

&lt;p&gt;What I Built&lt;/p&gt;

&lt;p&gt;What if AI could remember the things we forget?&lt;/p&gt;

&lt;p&gt;At Cal Hacks 13.0, my team and I built RecallAI, an AI-powered visual memory assistant designed to help people remember where they last saw their belongings and retrieve those memories through natural conversation.&lt;/p&gt;

&lt;p&gt;We’ve all experienced that frustrating moment when we can’t find our keys, headphones, wallet, or something else important. Instead of searching everywhere, imagine simply asking:&lt;/p&gt;

&lt;p&gt;“Hey RecallAI, where did I last see my AirPods?”&lt;/p&gt;

&lt;p&gt;And getting a response like:&lt;/p&gt;

&lt;p&gt;“Your AirPods were last seen on your desk 23 minutes ago.”&lt;/p&gt;

&lt;p&gt;That’s the idea behind RecallAI.&lt;/p&gt;

&lt;p&gt;How It Works&lt;/p&gt;

&lt;p&gt;RecallAI combines computer vision, persistent storage, and an AI agent to turn everyday observations into searchable memories.&lt;/p&gt;

&lt;p&gt;Our architecture uses:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;YOLO for real-time object detection.&lt;/li&gt;
&lt;li&gt;Visual embeddings to recognise and distinguish registered personal belongings.&lt;/li&gt;
&lt;li&gt;SQLite to store timestamped observations and associated visual evidence.&lt;/li&gt;
&lt;li&gt;Claude to interpret natural-language questions and retrieve relevant memories.&lt;/li&gt;
&lt;li&gt;FastAPI to connect the computer vision pipeline, database, and user interface.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Rather than simply identifying objects, RecallAI builds a history of when and where those objects were observed.&lt;/p&gt;

&lt;p&gt;My Contribution: Temporal Memory&lt;/p&gt;

&lt;p&gt;One of my main contributions was developing RecallAI’s Temporal Memory system.&lt;/p&gt;

&lt;p&gt;Object detection answers the question, “What am I looking at?”&lt;/p&gt;

&lt;p&gt;Temporal Memory goes further by asking, “When did I last see it, and what do I know about its history?”&lt;/p&gt;

&lt;p&gt;The system uses timestamped visual observations to support capabilities such as:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Last-Seen Recall&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Ask when an item was last observed and retrieve its most recent recorded sighting.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Historical Memory&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Search previous observations to understand where an object appeared at a particular point in time.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Time-Aware Queries&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Retrieve objects based on elapsed time, such as belongings that haven’t been observed recently.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Natural-Language Retrieval&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Connect historical observation data with the AI agent so users can ask questions conversationally.&lt;/p&gt;

&lt;p&gt;A particularly important engineering consideration was distinguishing what the system actually observed from what it could only infer.&lt;/p&gt;

&lt;p&gt;For example, an object disappearing from the camera’s view doesn’t necessarily mean someone moved it or left it behind.&lt;/p&gt;

&lt;p&gt;By grounding responses in recorded observations, we aimed to make RecallAI’s memory useful without overstating what the camera actually knew.&lt;/p&gt;

&lt;p&gt;Beyond Objects: Remembering People&lt;/p&gt;

&lt;p&gt;We also explored a broader vision for RecallAI: helping people maintain meaningful relationships.&lt;/p&gt;

&lt;p&gt;Imagine registering a friend, with their consent, through a scan or manual entry.&lt;/p&gt;

&lt;p&gt;RecallAI could remember when you last connected and gently remind you when it’s been a while.&lt;/p&gt;

&lt;p&gt;For example:&lt;/p&gt;

&lt;p&gt;“It’s been three weeks since you last caught up with Alex. Maybe it’s time to reach out!”&lt;/p&gt;

&lt;p&gt;This expands RecallAI’s potential beyond finding belongings into helping people stay connected.&lt;/p&gt;

&lt;p&gt;Our vision is simple: AI shouldn’t just help us remember things. It should help us remember what matters.&lt;/p&gt;

&lt;p&gt;Demo&lt;/p&gt;

&lt;p&gt;GitHub Repository: &lt;a href="https://github.com/Slickstarlol/CalHacksObjectFinder" rel="noopener noreferrer"&gt;https://github.com/Slickstarlol/CalHacksObjectFinder&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Demo Video: [Insert your video or Devpost demo link]&lt;/p&gt;

&lt;p&gt;A typical RecallAI workflow looks like this:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Register a personal belonging.&lt;/li&gt;
&lt;li&gt;Allow the camera to recognise it during normal use.&lt;/li&gt;
&lt;li&gt;Store its observation history, including timestamps and snapshots.&lt;/li&gt;
&lt;li&gt;Move the item outside the camera’s view.&lt;/li&gt;
&lt;li&gt;Ask RecallAI when and where it was last observed.&lt;/li&gt;
&lt;li&gt;Receive a time-aware response grounded in the recorded evidence.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The result is an interface that transforms camera observations into memories users can actually retrieve.&lt;/p&gt;

&lt;p&gt;Partner Technologies&lt;/p&gt;

&lt;p&gt;Our project brought together several technologies, each responsible for a different part of the memory pipeline.&lt;/p&gt;

&lt;p&gt;Computer Vision: YOLO enabled object detection, while visual embeddings helped match observations against registered belongings.&lt;/p&gt;

&lt;p&gt;Claude: Provided the conversational layer, allowing users to ask questions naturally instead of manually searching through recorded observations.&lt;/p&gt;

&lt;p&gt;FastAPI and SQLite: Connected the system’s components and provided persistent storage for the historical memory layer.&lt;/p&gt;

&lt;p&gt;MLH Partner Technology: [Add any official MLH partner technology your team actually integrated, including the API, SDK, implementation details, challenges, and what you learned. If none was used, state that clearly.]&lt;/p&gt;

&lt;p&gt;One of the most valuable technical lessons was learning how to integrate different AI components into one coherent application. Detection, recognition, storage, retrieval, and natural-language interpretation all needed to work together.&lt;/p&gt;

&lt;p&gt;Hackathon Experience&lt;/p&gt;

&lt;p&gt;Building RecallAI at Cal Hacks 13.0, hosted in Berkeley, California, was an incredible experience.&lt;/p&gt;

&lt;p&gt;What stood out to me was the atmosphere: being surrounded by ambitious builders, developers, and students who were genuinely excited about creating things.&lt;/p&gt;

&lt;p&gt;Coming from the University of Birmingham in the UK, travelling to California for Cal Hacks was an opportunity to experience a completely different technology ecosystem.&lt;/p&gt;

&lt;p&gt;My team and I had to make decisions quickly, divide engineering responsibilities, integrate our work, and turn an idea into something tangible within the hackathon’s limited timeframe.&lt;/p&gt;

&lt;p&gt;We also learned that a compelling project doesn’t necessarily need to solve every problem imaginable. Sometimes the strongest approach is identifying one meaningful problem and building a focused solution around it.&lt;/p&gt;

&lt;p&gt;For RecallAI, that problem was memory.&lt;/p&gt;

&lt;p&gt;Working on Temporal Memory was particularly rewarding because it connected the technical infrastructure of our application with something users could immediately understand: being able to ask where something was and receive an answer based on actual observations.&lt;/p&gt;

&lt;p&gt;Beyond the code, Cal Hacks reminded me why I enjoy software engineering in the first place.&lt;/p&gt;

&lt;p&gt;It’s the process of taking an idea, collaborating with other people, encountering unexpected problems, and eventually seeing something you built come to life.&lt;/p&gt;

&lt;p&gt;What’s Next?&lt;/p&gt;

&lt;p&gt;RecallAI has potential applications beyond locating everyday belongings.&lt;/p&gt;

&lt;p&gt;We want to explore richer historical search, more reliable context-aware reminders, and ways to help people maintain their personal connections.&lt;/p&gt;

&lt;p&gt;Ultimately, we’re interested in one question:&lt;/p&gt;

&lt;p&gt;What if technology could help us spend less time searching for things we’ve forgotten and more time focusing on the people and experiences that matter?&lt;/p&gt;

&lt;p&gt;That’s the future we started exploring with RecallAI.&lt;/p&gt;

&lt;p&gt;⸻&lt;/p&gt;

&lt;p&gt;Built at Cal Hacks 13.0.&lt;/p&gt;

&lt;p&gt;GitHub: &lt;a href="https://github.com/Slickstarlol/CalHacksObjectFinder" rel="noopener noreferrer"&gt;https://github.com/Slickstarlol/CalHacksObjectFinder&lt;/a&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  CalHacks #MachineLearning #ComputerVision #AI
&lt;/h1&gt;

</description>
      <category>mlhacks</category>
      <category>devchallenge</category>
      <category>hackathon</category>
    </item>
  </channel>
</rss>
