Ffoundly.
01 · A QUICK QUESTIONTHINK ABOUT YOUR LAST TIMEHave you ever lost
TIME: 0:00–0:15
SAY: Have you ever lost something at university? Maybe your keys, your wallet, or your student card? Where did you look first? And how did you know where to go?
DO: Look at the audience. Pause briefly after the first question. Allow a quick response or a show of hands.
TRANSITION: For many of us, the first step is a Facebook group.Have you ever lost
something at university?
🔑 Your keys?👛 Your wallet?🪪 Your student card?
Where did you look first?
How did you know where to go?
Ffoundly.
02 · THE FACEBOOK SEARCHTHE SEARCH BEFORE FOUNDLYLost your keys.
Lost your keys.
Now what?
You post in a Facebook group.
Then you wait for the right person.
↓Your post competes with newer posts.
👀The finder may never see it.
📍You may still need to ask where it is.
A useful post can be easy to miss.
User-provided Facebook example
Original screenshot · 18 October 2023
Ffoundly.
03 · ASKING AROUNDTHE OTHER WAY TO SEARCHAsk here.
Ask here.
Walk there.
Ask again.
You check a counter.
Then another office.
Then ask someone nearby.
⌛Each visit takes time.
❓You still do not know who has it.
🚪You need to reach the right place.
Counter→Another office→Ask again
AI-generated illustration · Fictional people and location
Ffoundly.
04 · MEET FOUNDLYMEET YOUR SOLUTIONMeet
Open the live app ↗
Meet
Foundly.
Check first. Then go.
Scattered posts→One searchable place
Unclear location→A reported map pin
Repeated questions→Chat and a clear meetup
Check reported items anywhere with internet access.
Screens and technical details for review →Actual Foundly screen · Reported items, not live tracking
Ffoundly.
REFERENCE · FOR REVIEWTwo needs.
One clear map.
🤲Found items — help find the owner.
🔎Lost items — ask others to help.
⌕Search by item, category, date or area.
⛶Open map-only mode. Tap an emoji.
Lost-item pins can show a likely loss location
or the last place the owner remembers.
Actual app screens · Demo data · Click to enlarge
Ffoundly.
REFERENCE · FOR REVIEWA useful post.
Four simple steps.
1Choose lost or found.
2Add details, photos and an emoji.
3Choose the date and map location.
4Review contacts, then publish.
Up to three photos · Found-item posts need a photo.
Review any public contact details before publishing.
Actual app screens · Demo data · Click to enlarge
Ffoundly.
REFERENCE · FOR REVIEWSee the details.
Find a possible match.
🖼️Open photos, dates, location and status.
↗Share the post or use listed contacts.
🧩See possible matches and the reasons.
💬Start a chat or a private claim.
Matches compare category, color, dates and distance.
People still check ownership before a return.
Actual app screens · Demo data · Click to enlarge
Ffoundly.
REFERENCE · FOR REVIEWTwo people.
One conversation.
AFinder — the person holding the item.
BOwner — the person asking for it.
✓Your messages on the right. Theirs on the left.
🔔Photos, unread badges and message status.
Each private conversation belongs to a post.
Ownership details stay inside the conversation.
A · Finder
B · Owner
Same conversation · Two accounts · Tested in two browsers
Ffoundly.
REFERENCE · FOR REVIEWAgree on one place.
Then get directions.
📍Pick a map point and a clear landmark.
🗓️Choose a future meeting time.
🤝The other person agrees or suggests a change.
↗Open the route in Google Maps.
Where the item was found
can be different from where you meet.
Actual app screens · Demo data · Click to enlarge
Ffoundly.
REFERENCE · FOR REVIEWBack in the
right hands.
1The owner sends private identifying details.
2The finder reviews and accepts the claim.
3Both people confirm the handover.
✓Returned items leave the active map.
A lost-item owner can also mark a post resolved,
including a return arranged outside Foundly.
Prepared returned example · No reset needed
Ffoundly.
REFERENCE · FOR REVIEWLess searching.
A clearer way home.
👤Account, profile and password settings.
📋Edit posts, close them and view return history.
🛡️Report, block, or remove a chat from your list.
🌐Use the same service on phone or browser.
Check online. Contact the finder. Plan your visit.
View the technical appendix →Actual app screens · Demo data · Click to enlarge
Ffoundly.
REFERENCE · FOR REVIEWThe stack behind Foundly
Technical reference for the instructor. Read after the live app demonstration.
🖥️
Web interface
React · Vite · TypeScript
Tailwind CSS + custom CSS
React Router · TanStack Query
🗺️
Maps and location
Leaflet · OpenStreetMap tiles
Emoji pins and map clusters
On-request GPS · Google Maps links
📱
Installed iPhone app
Expo · React Native · WebView
Shares the web interface
Installed with Xcode on iPhone 15
⚙️
API and chat updates
NestJS · REST /api/v1
Socket.IO update events
Server-side access and data checks
🗃️
Database and images
PostgreSQL · Prisma
Sharp resizing and metadata removal
Persistent image storage
☁️
Delivery and testing
Docker Compose · VPS
Nginx · HTTPS · Backups
Playwright + API integration tests
Ffoundly.
REFERENCE · FOR REVIEWDifferent devices. Shared data.
📱
Phone
Read posts or send a message
💻
Another browser
See the post or receive the reply
↔
HTTPS · NGINX · VPS
NestJS API
Check identity and access.
Validate data and state.
Save before confirming success.
/api/v1 · Socket.IO↔
🗃️
PostgreSQL
Accounts, posts, messages,
claims and meetings
🖼️
Persistent images
Public post images
Access-controlled private images
Message flow: Send with a message ID → Check room membership → Save to the database → Confirm → Notify the other person
After a disconnect: Fetch missing messages and retry using the same ID to avoid duplicate saves.
TECHNICAL REFERENCE — FOR REVIEW
An image upload is checked and processed before use. The post request is validated through the API, structured fields are saved in PostgreSQL, and image files are stored in persistent storage. Other devices use the same API.
Messages are saved before a successful acknowledgement. Socket.IO is the update signal, not the database. If a response is lost, the client can check the original message ID before retrying.
The phone needs internet access for current shared data. It does not need to be on the same Wi-Fi as the Mac. The installed Release app does not need Metro or the development computer to keep running.After a disconnect: Fetch missing messages and retry using the same ID to avoid duplicate saves.
Ffoundly.
REFERENCE · FOR REVIEWFrom a report to a return
01 / POST
→Report an item
FOUND or LOST
Photos, category, date, location
Starts as OPEN
02 / DISCOVER
→Find a lead
Area, category and date filters
Clusters based on zoom
Suggested opposite-type posts
03 / CLAIM
→Check ownership
Private two-person room
Identifying details
One accepted claimant at a time
04 / RETURN
Meet and confirm
Agree on a place and time
ARRANGING while returning
Both confirm → RETURNED
Other paths: Cancel where allowed · Restart a cancelled claim in the same room · Resolve a LOST post after recovery
Core data: User · Session · Post · PostImage · ContactChannel · Place · Conversation · Message · Claim · Meeting · Block · Report
Core data: User · Session · Post · PostImage · ContactChannel · Place · Conversation · Message · Claim · Meeting · Block · Report
The reported item location and the private meeting location are separate records.
TECHNICAL REFERENCE — FOR REVIEW Active FOUND posts include OPEN and ARRANGING. LOST posts are displayed separately while OPEN. Returned items leave the normal map. Claim acceptance checks access and current post state inside a transaction to avoid multiple accepted claimants. Meetings have a version and require renewed confirmation when changed. Both participants must confirm a handover before a found-item post becomes RETURNED. The owner can mark a lost-item post RESOLVED after recovery. Possible matches compare opposite post types, category, color, date range and distance. They do not provide a tested accuracy percentage or automatically verify ownership.Ffoundly.
REFERENCE · FOR REVIEWReady for a pilot. Room to grow.
Available now
✓ Accounts and protected sessions
✓ Posts, images, chat and meeting pins
✓ Private claims and return confirmation
✓ Reports, blocking and role-based review
✓ HTTPS, persistent storage and backups
Current limits
• Internet is needed for shared data.
• Unreported items cannot be shown.
• There is no continuous GPS tracking.
• No push alerts while the app is closed.
• More physical-device testing is needed.
Recent presentation checks: Two accounts in Chromium and WebKit, live message delivery, map links, form screens and profile screens.
Earlier project evidence: API access checks, browser flows and isolated backup/restore tests. Not all tests were rerun for this deck.
TECHNICAL REFERENCE — FOR REVIEW
Sign-up uses a username and password, with administrator-assisted recovery during the pilot. Passwords are hashed with Argon2id. The web session uses HttpOnly cookies and CSRF checks for writes.
Private rooms and images require access checks. Authorized administrators can review reported content according to their role. Removing a chat from one list does not erase the other person's history.
The VPS stores shared data and persistent images. The project has backup and restore tools, but wider device testing and operational improvements remain future work. Do not claim guaranteed uptime, guaranteed recovery, App Store approval or full large-scale readiness.
The Facebook screenshot is user-provided historical material. The counter image is an AI-generated illustration. App screenshots are genuine demo-account browser captures. No claim is made that all Facebook posts or all university counters have the same limitations.Earlier project evidence: API access checks, browser flows and isolated backup/restore tests. Not all tests were rerun for this deck.