Put births, moves, houses and photographs on one dated timeline, see the places on a map, and let the relatives who remember fill in what you cannot.
A family tree says who. A timeline says when — and it is usually the when that turns a list of names into something anybody wants to read.
The events a family history is made of
Births, marriages, moves, houses, jobs, arrivals and departures: each one a dated event with a place, whatever you have found out, the people it involves, and the photographs and documents that belong to it. The place is a real coordinate, so the map draws the moves rather than listing towns.
Dates that are ranges stay ranges. "Lived in Lviv, 1946 to 1961" is one event with a start and an end, not two guesses at a single day.
Photographs that date themselves
Drop in a folder of scans or phone photographs and Boromlia reads the date and location out of the files, clustering them into events you then name. HEIC files from an iPhone are converted on the way in. What a digitised shoebox mostly needs is dates, and most of the dates are already in the files.
Letting the family in
A timeline can have collaborators — the aunt who knows which house that was — who add events alongside you. On Advanced, a read-only link lets the rest of the family read it without an account, and an iframe puts it on a family site.
Nothing is public until you decide. A family history usually stays private or shared by link; making it public is a separate choice, and public timelines are the ones listed in the examples catalogue.
Views worth leaving open
River: A generation reads as a line, with the photographs either side of it.
Map: Every move, in order, on one route — the shape a family history usually has.
Cards: A decade at a glance, when you are still filling in the gaps.
Questions
Does it import a GEDCOM file?
No. Boromlia records dated events, not a tree of relationships, so there is no GEDCOM import and no relationship model. What it does read, on Advanced, is a CSV or TSV of events with the columns matched to fields by hand.
Can I keep a source for each fact?
Yes. Every event has its own source field — a certificate reference, an archive fonds, a link — and "has a source" is one of the filters.
What happens to the photographs?
They stay with the events and come back out again: the photo export writes a zip of every image, numbered in timeline order, with a manifest saying which event each one belongs to.