Frais

Company: Frais

Self-reported basis: The description is entirely self-reported by the author, unverified, and lacks any independent corroboration.

What it appears to be: A mobile web application that helps users find cooler walking routes during extreme heat by integrating geospatial data, LiDAR, weather, and solar geometry.

What changed: The project was submitted as part of a hackathon, suggesting early-stage development and prototyping.

Single most important open question: Is there evidence of user adoption or traction beyond the prototype phase?

The description states that Frais is an app that helps users find shaded or cooler walking routes during extreme heat. It compares pedestrian routes based on:

• Time and distance;
• Estimated shade percentage of the route;
• Estimated coolness;
• Departure time and sun position;
• Proximity to trees, buildings, water points, and crossings.

It displays a map, allows route selection, and offers step-by-step guidance with geolocation. The app is built as a mobile web installable application using OpenStreetMap, Leaflet, OSRM, and LiDAR data from the IGN.

Evidence: Self-reported by author.

Confidence: Low — no independent verification or demonstration of functionality beyond prototype stage.

The project is positioned as a tool to improve pedestrian comfort during heatwaves by leveraging advanced geospatial data. The author claims it goes beyond simple route optimization, focusing on thermal comfort and user experience.

It also emphasizes honesty in its approach — acknowledging that when data is missing, the app does not pretend to be precise.

Evidence: Self-reported by author.

Confidence: Low — no external validation or market positioning data provided.

The description implies a target audience of pedestrians who are sensitive to heat, particularly during extreme weather events such as heatwaves. The app is designed for use in urban environments where shade and temperature can vary significantly.

It was initially tested in Prades-le-Lez and aims to expand to Montpellier Méditerranée Métropole.

Evidence: Self-reported by author.

Confidence: Low — no explicit customer segmentation or user research data provided.

No business model or pricing information is provided in the description.

Evidence: Not evidenced.

Confidence: None.

The app uses:

• OpenStreetMap and Leaflet for mapping;
• OSRM for route calculation;
• LiDAR data from IGN to estimate shade;
• Weather and solar geometry data;
• Mobile web installable format (PWA).

It was built using ChatGPT and Codex, according to the author.

Evidence: Self-reported by author.

Confidence: Low — no demonstration or technical architecture details beyond basic stack.

The project is described as a hackathon submission, indicating early-stage development. It has not been demonstrated in production or with real users beyond local testing in Prades-le-Lez.

No evidence of user adoption, revenue, or customer base is provided.

Evidence: Self-reported by author.

Confidence: Very low — no traction data.

The description does not mention any competitors or similar products. It is unclear whether there are existing tools for optimizing pedestrian routes based on heat or shade.

Evidence: Not evidenced.

Confidence: None.

• Unverified claims: The app’s functionality and accuracy are self-reported without independent validation.
• Limited scope: Only tested in one small town, with no indication of scalability or expansion plans.
• Technical limitations: Challenges with LiDAR data precision, mapping inaccuracies, and computational costs were noted.
• No monetization strategy: No business model or pricing structure is described.
• Prototype-only status: The project is presented as a hackathon prototype, not a product in development.

Evidence: Self-reported by author.

Confidence: Medium — based on the description’s acknowledgment of technical and data challenges.

1. What are the actual limitations of the LiDAR-based shade estimation in real-world conditions?
2. How do you plan to scale this beyond Prades-le-Lez and Montpellier?
3. Have you conducted any user testing or feedback collection from end users?
4. What is your roadmap for monetization or sustainability?
5. Are there any partnerships or data sources that could improve the accuracy or scalability of the app?
6. How do you plan to handle edge cases, such as temporary closures or changes in urban infrastructure?