Mental BoundMental Bound
EL
Real Estate

e-akinito — Every fault and repair, with its proof

Our own mobile app: a private record of a building's condition and history. The owner records the building space by space, logs each fault and repair from a list, and attaches its proof: a photo, an invoice or a report. Each entry's credibility comes from that evidence, not from who wrote it, and the timeline never hides an edit. In private testing on Android, in Greek and English.

Full-Stack DevelopmentUI (User Interface)UX (User Experience)Data Residency
Software DevelopmentIntelligent Web Experiences
Visit website
e-akinito.com/en
The e-akinito landing page: the headline Every fault. Every repair. With its proof., the status In private testing · Android, and an elevation drawing of an apartment block with a revision cloud on a third-floor bathroom window, beside a timeline card for its water heater
The landing page on a phone: the headline, the description, the two buttons, the status and the top of the drawing
The landing page: the promise, the status and the example entry, pinned to an elevation drawing.

At a glance

evidence tiers
3
Owner, Trade and Inspector, earned by the photo, invoice or report on the entry
lost versions
0
An edit becomes a new version; the earlier one stays visible
reader
1
Only the owner sees the record; nothing is published
languages
2
Greek and English, in the app and on its landing page

What we built

The app

Flutter · Android
  • Add a building, then its spaces (kitchen, bathroom, balcony, storage) and what each one holds (water heater, boiler, air conditioner, windows): anything that deserves a history of its own.
  • Log what happened by picking it from a list: leak, crack, damp, repair done, replacement. A date and, if you like, a condition from 1 to 5. Typing is only for what isn't on the list.
  • Attach the proof: a photo from the camera, or an invoice or a report as a PDF, opened inside the app.
  • The tier belongs to the entry, not the person. A photo or a note is the Owner tier, an attached invoice lifts the entry to Trade, a report to Inspector. No credentials are checked.
  • A timeline of the whole building, newest first, filtered by space and component.
  • Greek and English throughout.

A record that hides nothing

Supabase · Frankfurt
  • An edit becomes a new version, and the earlier versions stay visible.
  • Removing evidence leaves a trace: the history shows who added or removed each file, and the tier changes with it.
  • Conflicting observations both stay on the record.
  • Only the owner sees the record: row-level security on every table of the Postgres database, tested with pgTAP.
  • Sign-in with an email and a six-digit code. No password.
  • Photos and PDFs sit in private storage and open only through links that expire.
  • The database and the files are hosted in the EU, in Frankfurt.

The landing page

e-akinito.com
  • Static HTML and CSS on Vercel: Greek at the root, English at /​en.
  • Self-hosted fonts, no analytics, no cookies.
  • An elevation drawing of an Athens apartment block carries the example: a leaking water heater in a third-floor bathroom, its repair, and the invoice that raised the entry to the Trade tier.
  • It says plainly where the app stands: in private testing on Android.

From the building to the proof

  1. Owner

    Building

    Add the property and pick its spaces: kitchen, bathroom, balcony, storage.

  2. Each space

    Components

    Water heater, boiler, air conditioner, windows: each gets a history of its own.

  3. From a list

    Observation

    Leak, crack, damp, repair, replacement. A date and, if you like, a condition from 1 to 5.

  4. Photo, invoice, report

    Proof

    The evidence attached sets the entry's tier: Owner, Trade or Inspector.

  5. Every version kept

    Timeline

    The entry joins the building's timeline. Edits add versions; the earlier ones stay visible.

Screens

e-akinito.com/en#how
How it works: four steps (your building and its spaces, what each space holds, what happened, the proof) above the chain building, spaces, components, observations, evidence
Four steps, mostly picked from a list.
e-akinito.com/en#tiers
The tier section: three cards stamped Owner, Trade and Inspector for a note or photo, an invoice and a report, and an example about Maria and the plumber's invoice
The tier belongs to the entry: a note or photo, an invoice, a report.
e-akinito.com/en#timeline
The timeline section: the history of a water-heater repair, with version 2 edited by Maria, an invoice added that moves the tier from Owner to Trade, and version 1
The timeline hides nothing: versions, files added or removed, the change of tier.
e-akinito.com/en#privacy
The privacy section: only you, no password, private files and data in the EU
Private by default: only you, no password, private files, data in the EU.

Built with

  • Flutter
  • Riverpod
  • Supabase (PostgreSQL)
  • pgTAP
  • Resend
  • HTML & CSS
  • Vercel

Ready to get started?

Tell us about your goals — we'll propose milestones within 48 hours.

Start your projectTry the Project Planner