Europe-wide private scouting workflow

Private porcini trip planning for Europe

Decide whether a forest is worth the drive, which ring to start with, and when your trip is most worth going — without turning your spots into a public hotspot map.

App coverage across Europe. Public sample pages stay ring-based and privacy-safe. Support: support@boletar.com
Three questions

Start with the user problem, not the feature list.

Boletar should first answer the three trip questions users already have in their head, then show which surface handles each one.

Is it worth going?

Predict

Use one pin to decide whether this forest deserves attention before you spend your weekend on false hope.

Which ring should I start with?

Area Scan

Compare rings around the center so your first walk starts in the strongest part of the area, not the most obvious one.

Which day is best?

Time Scan

Rank the coming days so you can choose the one outing window most worth the drive instead of guessing across the week.

Sample report

The sample trip report should be the main public product asset.

Safe by design, specific enough to be useful, and structured exactly like a real decision surface: no exact spot, but enough ring, timing, rule, and recommendation logic to understand why the product matters.

Public-safe report structure

One report can explain the product faster than a page full of claims.

The sample shows a ring-first layout, time ranking, rule card, and one explicit recommendation sentence. It is public enough to share, but still respects private scouting memory by never exposing an exact productive point.

No exact spot Location is framed as an area and ring structure only.
Time ranking The best outing day is ranked instead of implied vaguely.
Rule card Trip value is filtered through regulation before the drive happens.
Recommendation sentence

Worth saving as this weekend's first attempt.

That kind of sentence should appear right in the report. It turns the product from “interesting signal” into “clear action” without exposing a hotspot map.

Why private

Private by product structure, not just by marketing promise.

Experienced foragers do not want their scouting history absorbed into a public hotspot layer. This has to be explicit, not implied.

No public hotspot feed

No discovery loop built around public exact points.

Boletar is not trying to turn productive forests into a public observation map or social feed.

No forced spot sharing

Your productive memory does not have to become community content.

The workflow is built for private decision support, not for compulsory public contribution.

Your scouting memory stays yours

The product should strengthen personal memory, not dilute it.

Trip packs, saved reports, and later sync are designed around private repeated use in the forest.

Regulations

Rules matter before a trip, not after you already committed the drive.

Public regulation content should show the fields that matter operationally: country and region, checked date, official source, and the actual trip implication.

Country / region Germany / Bavaria example Users should know which legal layer they are reading, not just that “rules exist.” Geo field Visible first
Checked date Show when the page was last reviewed Rule pages should not look timeless if the public is supposed to trust them for trip planning. Recency field Operational trust
Official source Managing authority or official source visible Public summaries are not enough when protected-area or local restrictions can override the baseline. Source discipline Before-trip check
Trip implication Why the rule changes whether the outing is still worth doing The right outcome is not legal trivia. The right outcome is a better go / no-go decision. Decision layer Before departure
Offline forest use

Forest Trip Pack should be described as a field workflow, not just as “offline mode.”

The value is not technical capability by itself. The value is carrying one prepared trip into the forest, opening it without signal, and syncing what happened after the outing.

Before you drive Save this trip before you drive Lock one plan, one ring priority, and one timing call before leaving the city. Forest Trip Pack Pre-trip step
In the forest Open it in the forest without signal Do not depend on mobile coverage at the exact moment you need to orient the trip. Offline access Field use
After the outing Log what happened and sync later Field memory should return to the product after the outing, not disappear because signal was weak. Private memory loop Later sync
Pricing

Simple enough to understand in one glance.

Free builds trust. Weekend Pass or Trip Pass can be tested as the short-window unlock. Pro is the repeat-use layer for users who want better certainty across the season.

Free

See whether the trip deserves attention.

For first trust, basic scouting logic, and understanding the product before paying for stronger certainty.

See pricing
Weekend Pass / Trip Pass

Unlock a short field window.

For users who already have a likely outing and want the full workflow without annual commitment first.

Compare passes
Pro

Use the product across the season.

For repeated users who want better ring selection, better timing calls, and a stronger private memory loop.

See Pro
Weekend Window

Subscribe by country, region, and language.

This should be a concrete alert list, not a generic newsletter. Users tell Boletar where they scout and which language they want, then receive weekend-window updates relevant to that geography.

Specific geography, low-frequency updates, no generic newsletter volume.
Weekend Window saved

Your country and region preferences are on file.

We will use this list for rollout updates and future weekend-window emails only.