How Predict, Area Scan, and Time Scan work together
Understand the app as one decision chain instead of three disconnected screens.
Read firstThis is not a generic mushroom blog. Boletar research exists to help serious European users think better about workflow, timing, ecology, regulations, and sustainable handling before the next real outing.
The right reading order is not random browsing. Start with the workflow, then timing, then regulations. That gives new users the fastest trustworthy map of what Boletar is trying to solve.
Understand the app as one decision chain instead of three disconnected screens.
Read firstLearn why weather still has to be read against baseline climate and habitat memory.
Read secondSee why rule layers should sit inside trip planning rather than after a place already looks promising.
Read thirdBoletar research is strongest when every piece has a narrow job: explain one field idea, qualify one common mistake, or improve one part of the app reading order.
The right shape for this hub is not volume. It is a tight set of field briefs that make the app feel more trustworthy before a trip.
The long-term system is simple: one brief explains a field idea, one region page localizes it, and one rule page explains whether the trip still clears the friction layer.
Country-level habitat framing, likely friction points, and how to interpret Boletar inside a core DACH market.
Open region guideOwn-use logic, local restrictions, and what still has to be checked before a real collecting trip.
Open regulation pageEvery strong brief should route users back into a pin check, a ring comparison, or a timing decision.
See app workflowBoletar's product coverage is Europe-wide. The public site is simply using a smaller set of research and Germany-led example pages to explain the system clearly before every country page is published.