background

No one wants to forget important tasks. But in times like these, we easily get distracted. Let's help to set up easy reminders in an environment everyone can use right away and with no installation needed.

what it does

Create your reminder. Set timer. Print. Hang. Let everyone scan and let them be reminded.

From changing sheets to checking gear and supply – When an overwhelming amount of people gets hospitalized, makeshift hospitals will face a lot of pressure. We want to remove some of this pressure by enabling every healthcare personnel to set useful reminders on their own devices.

how it works

No installation needed. This is running as PWA and keeps tech low, but efficiency high. We split the main idea (create, print, hang, scan) into three micro-services hold together by a manager-API. The interface has simple steps of task creation and printing in mind. To achieve this the services communicate with each other the fastest way, pushing the data needed to a minimum. Scanning is done through the now-basic integration of QR-recognition in most smartphone devices.

based on

Architecture

  1. Backend: .NET Core + Java
  2. Frontend: React
  3. Meta: AMQP for messaging between components (micro-services)

our challenge

Quick team development was our first task. Luckily chemistry worked on our site.

Next up: Concept. We quickly decided to leave out overhead and to maximize our output by only assigning tasks we are capable of.

Validation of the idea was another big pain point. We talked to hospital personnel, to administration in healthcare, to crisis responders ... and we learned so so much. We might be even more greatful for these people in these jobs than ever before.

We decided: Finding a single use-case in a pandemic crisis is not the approach for our reminder PWA. We decided to broaden the perspective, after learning from each sector as much as we could. This influenced the architecture as well as the whole feature set itself. We don't just remind people of things to do, we help them do be reminded when they really need it – in a simple way.

team spirit

We're here to not only do "something", but find a way to help. This team has brought so much good intentions to the table and has worked closely together, to have everyone involved.

next up

We reached out to various companies to talk about the implementation on their side, mainly QR-code printing device manufacturers. Some of them in Germany, most of them internationally.

the crew

  • Nico: C#, Asp.Net Core, Angular, SQL/rel. DBs, Ionic
  • Jack: C#, ASP .Net Core & Angular, WPF, Xamarin
  • Marcel L: C# (.NET, .NET Core), Java, Angular, Javascript, PHP
  • Johannes S: JavaScript, VueJS, React, PHP, Go
  • Alex: Java, C#, Angular, React, RBDMS, Messaging, Docker, Jenkins
  • Frank: UX/UI-Design, Expertise in Reviews, Customer Journey, Persona Testing
  • Michael: Design/Motion Design, Concept, Animation & Video, CI/CD, Pitch Decks
  • Raiko: Concept, Text, Ideation & Creation, PM, Recruiting
  • Daniel: Java, Node, Python, React/Angular, SQL/NoSQL, OAS, Docker

Built With

Share this project:

Updates

posted an update

To the first finish-line: We are working hard on the last few things, to get the video ready for upload. We have all texts in place, graphics are created as I type. Developers are taking all steps necessary for the code to be ready at midnight. We also had some good talks with other teams and how to proceed further. This hackathon is a blast of an experience!

Log in or sign up for Devpost to join the conversation.

posted an update

We've collected team information for our presentation. Currently developing the video for our pitch and setting up a landing page for contacts. Backend is nearly finished, frontend needs some touch-ups. We're trying to reach out for first partners to play around with our ideas and to extend the value beyond our paper-approach to QR printing. Keeping you posted!

Log in or sign up for Devpost to join the conversation.

posted an update

First day (at least for this team) is over. We finished as much as we could in a sense where we met only minutes ago. Everyone knows what to do and where to pick up their tasks in the morning. I must say, that this has been an outstanding experience so far. From the overwhelming acceptance of different approaches, to the friction-less communication we had right from the beginning. With the backend divided into three micro-services and the manager API holding everything together, we have a rather good idea, about where we are heading. We also happen to have the first glimpses of our "branding", which started some "Wow"s in our call. The icing on the cake: A full UX-analysis on what this PWA needs to get done for the users.

Thanks so much for everyone asking about this project and for contributing their ideas! We'll keep you updated next thing in the morning.

Log in or sign up for Devpost to join the conversation.

posted an update

Backend architecture is looking good. Two frontend-developers are taking care of the visual experience. We found support from a designer who is currently developing an identity and who is challenging the way we look at the final outcome. Luckily we also found a UX-Designer. He is helping with the physical and digital touchpoints for users and reminds us to focus on the basics.

Let me say, that this is one really big tasks right now: Finding out what generates real value to the users. Why should they use a product, where they have to print out a code? We found, that especially the lightweight implementation through bring-your-own-device on the side of the "reminded" can change how we interact with the physical world. If not for this concept, it will for many others in the future.

New updates will follow soon.

Log in or sign up for Devpost to join the conversation.

posted an update

Team is all set and running. We reached out to medical personnel and hospital organization staff. They were outstandingly friendly and gave us terrific insights into their work. Send us a message, if you want to help or want to know more about it!

Log in or sign up for Devpost to join the conversation.