To-Do-List review

Three years ago I almost never touched modern web development. Just Drupal, WordPress and some old fashion html table layout. So my experience was limited. I had a vision to create a website interacting with Postgresql. So I started this journey with no or minimal luggage.

There are many ways to skin a cat (Mark Twain). That was amongst the hardest challenges to select amongst about a hundred tools and hundreds of ways to do the same thing. You have to master several tools and how they interact with each other. And create a VPS environment for hosting and managing things.

I did choose Go as the foundation that is not a common web tool despite about 2 million developers. I was familiar with Postgresql, but had no idea how to interact using a web browser. Another decision was to create a REST API in between the browser and the database. So far I am happy with my choices.

I put all things together in a simple draft of a To-Do-List.

How do the UX work for you?
Overall impressions?
Any comments and feedback are very welcome.


So far it seems clear to me, the main thing is that it has to be functional, easy to understand, and attractive to the eye.

Personally, if I have to work on such a project, I start by listing the requirements & functionalities, then design the interface according to my own ideas, then I look at what exists and try to retain the best of it.

I usually use Redbooth or Trello as my task manager, both of which are excellent.

It would require a number of essential features to be added to your tool: task categorization, user assignment and management, priorities, status, … but maybe all this is planned.

1 Like

Most - if not every - To-Do-Lists on the market are not suited for more or less disabled (font size 7-9px and light grey on white background for an example). My intention is to make a To-Do-List for people 40+ :slight_smile:

This is only a draft in order to get some feedback. Am I on the right track or do I have to rethink?

I don’t think there is a market for this. I also think people would rather download an app for something like this rather than use a website. As an experiment, learning exercise sure. However, I think it would be difficult to find anyone who would care to use this. Furthermore, I would highly recommend using lambdas instead of a dedicated server with nginx. The single nginx server is limited in its scaling potential where as lambdas auto scale to accommodate traffic needs and are pay for use rather than time that likely to be less hosting cost. Serverless computing is the future of apis simplifying deployment and automatically scaling with observabiity built in. Golang is well suited for serverless development because the language has a super quick start time. Golang is one of the fastest serverless languages.

" Serverless computing is a cloud computing execution model in which the cloud provider allocates machine resources on demand, taking care of the servers on behalf of their customers"

Translated into my brain this is a managed server. Isn’t it?

If you mean AWS Lambda it is more or less prohibited in Europe (GDPR)

We will see. There are maybe some 40+ out there :slight_smile:

I agree - there could be a market there. Sometimes the “kitchen sink” approach where a site/app does 9 Billion things isn’t needed. Sometimes simpler is better. And cloud doesn’t always have to be the solution, especially for a prototype. As long as you built the backend with the proper interfaces, you can switch to a more robust architecture if you need to.

I like the simplicity, and I think my wife would even find it something she’d be able to use (she’s a BIG to do list person, hates “web apps”, and is in your age demographic range :D)

As for what you’ve produced.

  • I personally find the site to be kind of…bright for lack of a better term. As an older person, I find the purple a little harsh. Perhaps tone down the brightness a bit. Or add another color (purple is a REAL hard color to do monochromatically)
  • It also feels like it needs a little bit more breathing room. A little bit more padding, a little more margin here and there.
  • Users seems unnecessary unless you’re planning on adding the ability to share to do lists later.
  • You probably don’t need to show the ids. Developers recognize them, and they make sense to us, but non-techies will not use ids - they’d use subjects, keywords, etc. Use those as the display drivers.
  • Is there more to the menu system? These seem redundant.
  • There is a minor bug when you’re in your mobile type of view. The edit/delete buttons go off screen.
1 Like

4 posts were split to a new topic: AWS lambda and GDPR

Thank you!

My intention is to create different themes in the future. Hope you will find any of them appealing. Prepared using color variables…

I will give this another thought.

Planned. But for now I just wanted to get some feedback that I am on the right track.


My experience is that you will add more functions in the future. Here is an example

Yes I am aware of this. This code seems not to be reliable:

const toright = window.matchMedia('screen and (max-width: 1500px)');
window.addEventListener("DOMContentLoaded", load);

toright.addEventListener('change', event => {
  if (event.matches) {
  } else {

function load() {
  switch (window.innerWidth < 1500) {
    case true:

Your feedback was appreciated! Thank you!

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.