Skip to main content
Home / Blog / Tafel.app: Why Good Ideas Sometimes Fail – and What We Learned
December 20, 2025 — Tobias Graupner

Tafel.app: Why Good Ideas Sometimes Fail – and What We Learned

Tafel.app: Why Good Ideas Sometimes Fail – and What We Learned

Transparency Note

This article is about a project we fully developed but that never went into production. We share our experiences because valuable insights can emerge from them.

What Was Tafel.app?

On behalf of Motus UG, we developed a comprehensive digital solution for Tafel Deutschland (German Food Banks) in 2025: Two mobile apps (customer app and scanner app for staff) plus a web dashboard for administration.

The idea was compelling: Digitize analog processes like customer management, queues, and eligibility verification. The calculated potential: over 300,000 saved volunteer hours per year with nationwide deployment.

What Happened?

In short: We built everything – but it never went into production.

The apps (customer app, scanner app) and the web dashboard were fully developed and functional. However, Tafel Deutschland decided against deployment. Our client (Motus UG) had assumed that Tafel would use the solution – that turned out not to be the case.

The reasons weren’t technical:

Miscommunication between client and end user (Tafel)
Decentralized structures each food bank decides independently
Resistance to change in established processes
No binding commitment before project start

What We Learned Technically

Flutter Proved Itself

Our decision for Flutter was right. In just 2 months, we developed two complete apps for iOS and Android – with one codebase. Performance was native, development efficient.

Takeaway: For cross-platform apps with limited budget, Flutter is a solid choice.

Privacy by Design Saves Time

We developed GDPR-compliant from the start: data minimization, automatic deletion periods, granular access rights. This cost more time initially but saved trouble later.

Takeaway: For sensitive data (social data, health), Privacy by Design is mandatory – and more efficient long-term.

Offline-First is Complex but Doable

The app had to work without stable internet connection. The synchronization logic was challenging but solvable with local data storage and intelligent conflict resolution.

Takeaway: Offline functionality significantly increases complexity but is indispensable for many use cases.

What We Learned About Projects

Technical Excellence Isn’t Enough

A technically perfect solution is useless if the framework conditions aren’t right. Stakeholder management and timing are just as important as code quality.

Non-Profit is Different

Decision-making in social organizations is longer and more complex. Volunteer structures and democratic processes require patience and adaptability.

Pilot Projects Need Champions

A pilot project needs internal advocates who drive it forward. Without this “champion” on the client side, even the best concept is hard to implement.

Why We Still Show This Project

Some would say: A failed project doesn’t belong in a portfolio. We see it differently.

1The work was good – technically and conceptually
2Honesty builds trust – we're not an agency that only shows successes
3Learnings are valuable – for us and potential clients

If you’re planning a project in the social sector, we can draw from this experience. We now know better what matters – not just technically.

Conclusion

Tafel.app was a project with great potential that failed due to external circumstances. The technical work and learnings remain. For us as a team, it was an important experience: Not every good project gets realized. But every project – successful or not – makes us better.

Planning a Digital Project in the Social Sector?

We bring not only technical expertise but also the experience of what matters beyond technology.

Talk to Us