Sowmen Rahman
Sowmen Rahman


Sowmen Rahman

INTRODUCING HelpingHand👋 : An open source app powered by the HRN stack

INTRODUCING HelpingHand👋 : An open source app powered by the HRN stack

The platform where you help friends and make them too!

Sowmen Rahman's photo
Sowmen Rahman
·Jul 1, 2021·

6 min read

This is my submission for the #HarperDBHackathon

Through this blog post, I shall be introducing you to the making of and showcasing my open source app HelpingHand and also talk about the brief journey of the hackathon from my perspective.

WebApp link:

The subdomain helping-hand was taken, alas! 😢


HelpingHand is an open source app that was built to serve exactly one purpose: To help people who are in need of it. Every app user signs up on the app platform and then can find themselves open to helping people from various posts that the people have earlier made. This person can then reach out to these people if they feel that the post describes a problem that he/she/they can solve.

But there's a catch, if you're reaching out to a person you've never interacted before, both of your identities are kept secret, unless the post shares finds you useful and decides to make you his/her/their friend. In this way, nobody can know much about the person they are helping, unless both sides cooperate together.

When a user decides to make another user their friend, they can then view their posts either help seeking posts or social posts and chat with them on the context of the post. This is basicall what HelpingHand is. You can think of HelpingHand as a cut down version of StackOverflow, but users are anonymous until both users are ready.


Ever since I was a child, I have always wanted to help people. So I guess the idea for this project naturally sprung from the urge of wanting to help people, no matter how small the contribution might be. The idea might not be that much of a good one, but I really wanted to participate in a hackathon, and this was a golden opportunity for me to showcase my skills.


  1. Frontend - React.js
  2. Backend - HarperDB integrated REST API
  3. Hosting - Vercel
  4. Version Control - GitHub


If you're confused after reading the title of this post, don't question yourself because it seems like that at first. HRN would stand for HarperDB, React and Node.js. Now I'm pretty certain everyone's looking for the 'E' in the stack, but there isn't one.

Let me give you a little backstory to why I skipped the server for this hackathon. Although this hackathon ran for a decent 30 days, I built this app on just over 7 days starting on 24th June. As I had too much academic stress from my university, I realized building both the backend and the frontend won't cut it before the deadline. Fortunately enough, HarperDB came to the rescue.

Using it's awesome SQL/NoSQL integrated REST API, I was able to build the backend without needing an Express or HAPI server like I'd generally need. Don't get me wrong, this really isn't the best way of doing this, but it was the only way if I wanted to finish on time, considering the features I had planned.



Users signup as direct database users and communicate directly without the meddling of any server in between. However, this also means that people will have to create usernames that abide with the authentication rules provided by HarperDB, and it also makes the process of making batch read and writes more difficult as everything is done on the client-end. It's not ideal, I know.

Login page

Login page

Signup page

Signup page

Post sharing

Users are able to write posts and ask for help on the app. People can respond to these posts if they want to help them solve the problem. Posts can be of help type and social type. Only people you're friends with can see the social posts.

Post share


The top searchbar can be used to search for posts. Users may search targeting tags, title or description for posts.

Post search


The core of the app relies on the ability to chat with people and communicate solutions for a certain type of problem. Users are able to chat with each other accordingly, but identities are kept hidden until one is satisfied with the help he/she is getting from the other person.

User view for public posts

User public post view

Before a user messages a person for help response

Before user sends message to post

After a user messages a person who needs help

After user sends message to post After this, the help seeker can decide to reply or not as he wishes.


The app also has minor notification support for when someone adds you as a friend or sends you a message. Currently, the notification system is not based on a websocket or external webhook server, and only updates on page refreshes, but these are all problems that can be mitigated with time, more on that on the roadmap talk that follows!


Mobile-friendly and responsive layout

Thanks to some very handy breakpoint hooks and responsive layout binding, I was able to make this website fully mobile responsive.


As you may have realized, the project is far from completion (the fact that it's somehow working with only a week of work is amazing to me, all thanks to HarperDB). I am outlining some of the more important tasks for this project. These are however not arranged in any specific order, but however among all other things, I am seriously considering refactoring as the first priority. The tasks are

  • Refactor code (A LOT)
  • Implement clean architecture (this was a primary target, but got cut short)
  • Enable persistence for rest of the reducers, currently only auth reducer has persistence enabled)
  • Reduce client-side manipulation code, implement backend code for auth, and other GET and POST operations in an Express.js server
  • Implement support for adding custom media to posts
  • Implement websockets and mail support(depends on the server implementation)
  • PWA (progressive web-app)


I invite the community to collaborate on this open-source project, as I'll not be discarding the project after the hackathon. I shall be making changes to the UI and building the server as soon as I am able.


Working with HarperDB was a very unique experience as I could manipulate the database using both SQL and NoSQL languages. The main challenge I had faced was really the time constraint compared to the project's goal weightage since I started very late. One other thing I noticed about HarperDB was that it'd not let me run nested SQL queries, it always ended up with some error I couldn't solve. However, I managed to find alternatives anyhow. Working on this project made me realize my strengths and weakness specially considering database modelling and querying.


Share this