Search for a command to run...
Beginning journey on building cheap task manager quest
Hi there 👋
I'm an Indonesian who loves coffee and dogs!! Also, code sometimes.
Currently studying at Kyoto College of Graduate Studies for Informatics. 🏫
Work as Full-Stack Engineer
No comments yet. Be the first to comment.
Or: Why we stopped trying to build software for everyone, and built Lensiro just for optical shops. If you've ever walked into an optical shop in Indonesia to buy a pair of glasses, you probably didn'
How event-sourced ledger architecture eliminated stock discrepancies in our optical retail app
ホコリをかぶった12台のMacBookから、今では本番LLMトラフィックの4分の1を担う200ノードのAppleシリコンファームへ
From twelve dusty MacBooks to a 200‑node Apple‑silicon farm that now powers our live LLM traffic
Discover how integrating GitHub with Snowflake empowers seamless version control and collaborative workflows for managing your UDFs and procedures.
Around half a year ago, my team and I were doing a project that needed task management. We looked at major task management services, but it was too expensive, and we just needed simple features, like setting deadlines, assigning them to someone, and managing the completion of tasks. So we decided to build one.
Before jumping to code, we need to have a clear image of what we will build. To do that, I listed up what this application should be able to do.
Again, to have a clear image of our goal, we should have a rough idea of what our application will look like. So making UI design is an excellent start to doing that. We want to keep it simple, easy to use, and dark because everybody loves the dark user interface this day. I jumped to UI Hut for inspiration and started making my very own UI Design with Adobe XD.
In my opinion, there is no right or wrong in choosing what tech stack when building something. What I think is important is why do we use it. Here is our's task stack
AWS API Gateway & Lambda & DynamoDB for the backend. We work for a small number of people and do not plan on accessing it frequently. It will be a waste to deploy a whole server just for it. Serverless may be expensive in some use cases, but for low in-frequent access, it is perfect.
React for the frontend. We have our REST API in serverless, and I think it makes sense to use SPA for our application. The reason why do we use React is because I used to use React, and I love to react. After building it, we will deploy it in S3 together with Cloudfront.
React Native for the mobile when tasks are assigned or have a task over deadline, we want to be notified. While I think it is overkill to build a whole mobile application for it, it is an excellent chance to try new technology and have it with it.
I will be building this application in the next two or three months. I am excited to show how I create the application and how I think what and how it should be done.
Thank you for reading this post!
