Step 1
Requirements Analysis
KWMSys - Real Time Flood Warning Mobile App
Impact We Have Created Together
- Real time alerts enabled
- Data usage expanded publicly
- Manual monitoring reduced
- New digital service launched
When We Joined
We joined at the concept stage and supported the project from product definition through mobile app development and release.
Who This Is For
Businesses that want to build additional digital services using their own data with real time notifications, dashboards, and user specific customization.
Duration:
3 months, Partnership ongoing
Type:
End to end mobile app development with responsibility for concept, UI/UX, frontend implementation, QA, and App Store release while integrating with an external backend.
Tech stack:
Product Design
Flutter Apps
Product Design
Flutter Apps
252
Views
Thomas Kiess
CEO
- Idea
- Solution
- Key components
- Development Process
- Technology & Integration
- Main Features
- Main Challenge
- Advice We Give
- Most Special Step
Idea
KWMSys operates sensor systems for cities to measure river water levels and other environmental metrics.
This data was already collected and processed in the cloud, but access was limited to professional users.
The idea was to make this information available to a broader audience so that citizens could stay informed about flooding risks in real time. To strengthen the warning system, official German weather alerts from the DWD were integrated.
The challenge was not data availability, but using it efficiently and turning it into a public facing product that delivers clear, actionable information when it matters most.
Solution
We built a mobile application that connects to the existing cloud infrastructure and visualizes live sensor and weather data in an interactive 2D map.
Users can select locations, subscribe to warning areas, and receive push notifications when critical thresholds are reached.
The app transforms complex IoT data streams into understandable warnings, enabling fast awareness and proactive response without requiring technical knowledge from users.
Key components
Development Process
Step 2
Concept and Design
Step 3
Implementation
Step 4
Quality Assurance
Step 5
Deployment
We analyzed available sensor data, warning thresholds, and user scenarios together with the client and defined how information should be presented to non technical users.
A clear mobile UX was designed with a strong focus on map based orientation, warning visibility, and fast comprehension. User flows were validated early.
The Flutter app was implemented while integrating with the client's backend APIs. Extensive mocking was used to stay productive despite backend dependencies.
We tested warning flows, notification delivery, and map interactions across devices to ensure reliability under real world conditions.
The app was released to the App Stores and prepared for ongoing maintenance and feature expansion.
Technology & Integration
Technology
Product Design
Figma for product redesign and design systems.
Mobile Apps
Flutter for iOS and Android using a single codebase.
Integrations
- Google Maps (2D map visualization)
- Push Notifications
- DWD Weather Data
Main Features
Interactive Warning Map
The core of the app is an interactive 2D map that visualizes live sensor data and weather warnings. Users can see affected areas at a glance, understand severity levels, and explore details for specific locations (data measuring points).
The map based approach makes complex data immediately understandable and actionable.
Real Time Notifications
Users can subscribe to specific locations and warning types. When thresholds are exceeded or new alerts are issued, the app sends push notifications in real time.
This ensures users are informed immediately without actively monitoring data.
Multi Source Data Integration
The app combines IoT sensor data from the client's cloud with official DWD weather warnings.
This creates a more reliable and comprehensive warning system than relying on a single data source.
Personalized Warning Settings
Users can customize which locations (data measuring points) and warning categories they want to follow.
This keeps notifications relevant and avoids alert fatigue while maintaining safety.
Main Challenge
The main challenge was integrating a complex external backend without direct control over its development. Back-end availability was limited, and quick changes were often not possible.
To keep progress steady, we relied heavily on API mocking, clear interface definitions, and detailed documentation.
Aligning frontend and back-end expectations required structured communication and careful coordination to avoid blocking dependencies while maintaining product quality.
What We Learned
We learned that frontend and backend separation requires strict interface contracts and proactive documentation. Mock driven development keeps teams productive even with limited back-end access.
Why This Matters for Our Partners
These learnings help partners manage distributed development setups more effectively. They reduce risk, improve predictability, and keep delivery timelines stable despite external dependencies.
Our Advice
If front-end and back-end are developed separately, define interfaces early and invest in mocking. It protects timelines and reduces coordination friction.
Most Special Step
The most special part of this project was the vision behind it: transforming raw environmental data into a public safety product that anyone can use.
Making real time flood information accessible through a clear, intuitive UI required balancing responsibility, clarity, and trust.
Designing a map driven experience that surfaces relevant warnings instantly showed how data becomes truly valuable when it is presented in a way that empowers people to act.
Behance
Thomas Kiess
CEO
5.0
The team connected our existing cloud infrastructure to a user-friendly mobile experience without compromising quality. They translated complex data streams into actionable public warnings with care and precision. The collaboration felt professional, thoughtful, and aligned with our mission.
Other References
Every successful project leaves behind measurable results and a clear path forward.
The references below show how we work, what we deliver, and the outcomes our partners achieve with us.
STRATEGY
UI/UX
SAAS
WEB DEVELOPMENT
PCapital - How a Cybersecurity Expert Became a Software Company
Karoly Aczel
Founder & CEO, Perpetuum Capital Ltd.
The founding team had years of hands-on ISO 27001 consulting experience and knew exactly what companies needed to get certified - but everything was delivered manually, one client at a time. The gap was clear: companies wanting ISO 27001 certification were either paying expensive consultants for work that could be structured into a guided tool, or they were lost in documentation without any support. The idea was to build two things that work together: a professional website that builds trust and sells digital products, and a SaaS application called Sentinel that guides organizations through ISO 27001 certification and ongoing ISMS management without needing a consultant in the room.
One-person consultancy → platform business
Use case
STRATEGY
UI/UX
MARKETPLACE
OfficeActor - End-to-End Influencer Booking Platform
Marlon B.
Founder & CEO, OfficeActor
Marlon B. saw a clear gap in the market: companies wanting to collaborate with influencers had no structured way to find, evaluate, and book them. Everything happened through DMs, spreadsheets, and informal agreements. At the same time, influencers had no professional tool to manage incoming requests, track contracts, or get paid reliably. The idea was to build a two-sided platform that gives both parties a clean, structured workflow - from discovery to signed contract to payment.
0 manual booking steps
Use case
