Field data from Konstantins — 2026-07-06
Part of the «Waze для рыбалки» wiki · Status: done — field artifact
Related: Konstantins profile · 11 questions · P2P opportunity · Secret spots · Hub & integrations
The gist
- Konstantins sent two unprompted artifacts: his phone home screen and a screen-recording of a fishermen's WhatsApp group.
- His pre-trip ritual: Windy, Storm Radar, and the LVĢMC website. All three are weather. Zero fishing apps.
- The group «Viss par copi !!!» ("All about the catch!!!") is Latvian-language, active since April. People freely name the waterbody and area — never the exact spot.
- One scroll shows two rental requests: a boat on Lake Zebrus and an echo sounder for a day. P2P demand, observed live.
- "Any success on Lielupe?" is our product, executed by hand.
1. Pre-trip ritual
Home-screen screenshot (11:41): Windy and Storm Radar circled in purple, followed by a link to videscentrs.lvgmc.lv (LVĢMC — the state environment, geology and meteorology centre).
| Source | What it gives | Class |
|---|---|---|
| Windy | wind, waves, pressure — visual | weather |
| Storm Radar | precipitation nowcast | weather |
| LVĢMC (site) | official forecast, hydrology | weather |
Takeaway: the expert's preparation = conditions only. No bite forecast in the ritual. No community in the ritual. This confirms the honest-conditions-index bet (forecasting) and the LVĢMC open-data bet (hub & integrations) — the expert already visits that site manually. Our job is to slot into an existing ritual, not to invent a new one.
Side note: Delfi RUS on the home screen re-confirms Konstantins lives in the Russian-language media space, while the group below is Latvian.
2. WhatsApp group «Viss par copi !!!»
The video is an 89-second scroll covering Apr 2 → today. 12–17 members online midday. Participants appear as phone numbers, not saved contacts — a broad community, not a friend circle. Language is Latvian, with Slavic-named members (Oleksandr) writing in Latvian.
Tempo — counted from the date separators and message timestamps in the frames (Piotr's correction, Jul 6: the frames carry exact timestamps, no eyeballing needed). The video covers Mar 31 – Jul 6, ~14 weeks. ~60 visible messages, i.e. 4–6 per week on average; the median day is zero. The rhythm is bursty: a catch triggers a flare (photo report → "Kur?" → answer, all within hours; 2–3 messages on such days), then silence. Two long gaps: Apr 14 – May 24 — six weeks with only two system phone-number-change notices, and Jun 10–29 — three weeks of nothing. Even with 361 members the group lives in fits. This is the clearest confirmation of the project's main risk — liquidity: content is scarce even where the people are already gathered.
Observations
| Message (Latvian) | Translation | Signal |
|---|---|---|
| «Kādi panākumi Lielupē? Kas ir bijis copēt» | "Any success on Lielupe? Who's been out?" | a live bite-map query — manual, unstructured |
| «Kura rajona, ja nav noslēpums» → «Varkaļu Osta» | "Which area, if not a secret?" → "Varkaļi harbour" | precision norm: area named, spot never; polite "if not a secret" escape hatch |
| «lielakā 1.480» → «Kur?» → «tērvetes upē» | "biggest 1.480 kg" → "Where?" → "Tērvete river" | waterbody named openly |
| «Maza Juglā» → «Cik izmērs?» | "on Mazā Jugla" → "What size?" | report = river + photo; size gets asked |
| «Šodien Venta aiz Kuldīgas uz diviem 😊» | "Today Venta past Kuldīga, two of us" | "river + landmark" precision — volunteered |
| Elvis, today: looking for a boat to rent on Lake Zebrus; camping «Niedras» booked out for the weekend | — | rental ask #1: boat |
| Oleksandr: "where could one rent an echo sounder for a day?" | — | rental ask #2: echo sounder |
| Album «Cope Norvēģijas ezerā 4.04.26» → «Te jau vairāk pēc Murmanskas izskatās 🥶» | Norway lake trip → "This looks more like Murmansk" | long trips shared too; lively reactions 👍❤️ |
| "This message was deleted" | — | self-moderation exists |
2a. Group sizes (second batch of screenshots, 18:49–18:50)
In the evening Konstantins sent two more screenshots — the info pages of two groups, member counts circled.
| Group | Members | Media | What it is |
|---|---|---|---|
| «Viss par copi !!!» | 361 | 331 | the reports-and-chatter group (the one from the video) |
| «COPES TIRGUS 🎣» | 1 020 | 2 794 | gear marketplace: rule #1 — "listings for fishing and outdoor inventory only" |
Three takeaways:
- The marketplace group is ~3× the conversation group — by member count. We did not compare message activity: size ≠ liveliness (Piotr's caveat, Jul 6). Still, even as a demand counter it supports the research's core lesson: a transaction gathers people better than talk.
- 1,020 of 1,024 — the group has hit WhatsApp's ceiling. WhatsApp's hard limit is 1,024 members; demand no longer fits the tool. A purpose-built app has room to grow exactly where WhatsApp physically ends.
- Konstantins has BOTH groups muted. The expert is an on-demand reader, not a push consumer. An argument for quiet-by-default notifications — an open decision, not a rule (Piotr, Jul 6).
Side note: 361 + 1,020 are ready-made seed audiences for the survey and launch, reachable through Konstantins.
3. What this confirms
- "Verify exact — publish coarse" is already the community norm. People share at "waterbody + area" level and stop short of the spot on their own. Our public layer matches their habit — adoption risk is lower than we assumed. → Secret spots, principles
- LVĢMC is the right bet. The site in the expert's ritual is the one whose open data we plan to ingest. → Hub & integrations
- No fishing app in the ritual. The "angler's conditions in one screen" niche is empty even for an expert. → Forecasting, Phase 0
- P2P demand observed live. Two rental asks in one scroll: boat and echo sounder — both "who could offer?" with no ready answer. → P2P opportunity
- The community also lives in WhatsApp. Not just Facebook and forums. A Latvian group with Slavic-speaking members — the community split is softer than it looks online. → Latvia market
- The product request already exists, phrased by a user. "Any success on Lielupe?" is literally our app's main screen, currently implemented as a question into a chat plus waiting.
This partially closes the questionnaire item on pre-trip information sources. The remaining 11 questions still stand.
Limitations
- One scroll of one group.
- Latvian translations are ours, not Konstantins'.
- Tempo counted from frames taken every ~2 seconds. Adjacent frames overlap everywhere, so coverage looks continuous, but fast scroll stretches could have skipped messages. Treat the numbers as a lower bound.