Hacker News new | past | comments | ask | show | jobs | submit login
Show HN: Remember – A progressive Todo app (github.com)
100 points by sanchitnevgi on Dec 30, 2016 | hide | past | web | favorite | 36 comments

I think the link in the ReadMe to the article about the motivations for this project is a much better read: https://medium.com/@sanchitgn/what-ive-learnt-developing-a-m...

It clears up why he's using a boatload of libraries. Basically, he wrote it in such a way that you can save the page as a phone app/bookmark thing, and it'll work even if you're offline.

Does anyone else find this PWA thing extremely ironic or is it just my age showing? It seems like we're basically reinventing the days of Delphi and VB, but this time it's over the Internet.

With a proper sandbox, and on multiple platforms, at the expense of resource usage and annoying dev experience (matter of taste admittedly). So I'm not sure where your Delphi comparison comes from, which IMHO was the opposite on all those 4 counts: quick and easy-to-dev, but windows only and you never knew if that .exe you downloaded was just a Todo app or a virus, a browser toolbar or...

Hi swsieber, that's exactly what I going for!

The application is great but you illustrate perfectly what the web development is becoming, tens of files for just 3 features (add, edit, complete)

Perhaps it wasn't OP's intention to make the most elegant Todo application, but rather learn a a new set of tools while creating an application (s)he's rather familiar with?

Then again I actually have no idea.

You could easily write a VERY simple Todo application with the three features you mentioned (add, edit, complete) using an HTML file and some Javascript.

At first glance, I don't suspect OP is trying to create the best Todo application of all time.

I think you're correct:

"I built to learn about progressive webapps or PWA"

What is a "progressive" web app? Serious question!

EDIT: Thanks for the explanations!

Google's marketing term for websites that use Service Workers in a manner that allows the site to function while offline. The sites also have to publish a Manifest file with metadata like icons and a start URL to be considered a "PWA."

Before reading, I thought it was going to be an approach to todo lists, but it's merely "progressive" in the "progressive enhancement" sense.

It's essentially a sample app for the offline-first approach to application design.

OP here! You guessed right, I wanted to make a simple application with all the modern tooling available out there. My main objective was to learn :)

Exactly. I initially thought it was satire. A dozen external libraries and a special package manager to build something that can be written with equivalent functionality in 10 lines of bash.

I don't exactly get why this is posted here. It seems like OP did this for the sake of his own learning, and that's well and good. But this is not a particularly interesting project and doesn't do anything novel.

"...written with equivalent functionality in 10 lines of bash."

Hyperbole much?

The OP isn't claiming to have done more than gluing together a bunch of stuff. And I don't think I can install a shell script on my phone. And it won't have equivalent functionality.

Hi, I thought of this as a starting point I could use to build more complex apps. The idea was in no way novel. I just wanted to use the modern technologies out there.

The first time I saw this things I thought: well, Java programmers are coming to web development ...

There're too many over engineering that call itself "simple" .

Modern web development is turning into the bloated mess of enterprise java we tried to abandon in 1999.

Holy crap, the amount of libraries, uses React/Redux/Webpack and Firebase.

Interesting, and it did most things I expected intuitively.

One missing piece though...I expected to be able to move items up or down in order. Basically sorting the to-do list. That doesn't appear to work.

Hi, There are a lot of features missing (Reordering, lists maybe). I focused on deploying as fast as possible and then adding features along the way. Also my motive my learning and not the application itself (There are a lot of todo apps out there already)

Also, I'd like to be able to clear my completed list, or something like that. That's gonna get cluttered real quick

Why someone needs "The big ones" plus 9 other libraries to do this? And a package manager!

At this moment, the top comment points to the explanation. TL;DR: The author is learning how to do PWAs.

Why "progressive" application needs to be so bloated?

It does what it promises. One thing I miss is the option to un-complete a task. Besides that, it's pretty pretty.

I like the the visual style, very minimalistic.

The "progressive" part of this is all Firebase.

Firebase handles your offline database, and syncing it for you automatically when you are reconnected.

The animation into 'completed' is a little too jerky imo. Also the concept looks very similar to 'clear'.


I see Firebase being used often around here to host progressive apps. Is there something that Firebase offers that is conducive to build progressive apps?

It seamlessly handles a changing network connection. When there's no internet connection, you still get to use the local database, and when there is a connection it'll sync everything with the server.

Missed opportunity to call it 'Member :P


We've banned this account for violating the HN guidelines. If you'd like it not to be banned, you're welcome to email hn@ycombinator.com. We're happy to unban accounts when people give us reason to believe they'll follow the rules in the future.



If you can't provide proper criticism, then keep your opinions to yourself. This is a simple Todo app that OP built as a side project, not sure what you were expecting.

It is called "simple, easy and intuitive UI". It is the ultimate dream of every designer and product manager.

Please go back to your cave to brush bits and bytes in assembly.

I get the heated response to the comment, but I'm not sure you can state this is "the ultimate dream of every designer and product manager". It is very simple and easy, but there are a lot of features missing (swipe left to undo for example).

Also, don't hate the bits & bytes in assembly, some HN readers read assembly and write bit operations on a daily basis. Those who write UIs in assembly are probably masochists. :)

I meant that easy and intuitive UIs, in generic, are the dream/goal of designers/managers, not necessarily this one in particular, since ToDo apps are so simple.

You made a good point about low level programmers. As a former assembly programmer that did lots of bit operations on 80386 processors I do understand your point. My apologies.

$ yarn start

yarn start v0.18.1

$ react-scripts start

sh: react-scripts: command not found

...The demo site looks cool, though :)

To get the react-scripts command, you'll need to globally install the react-scripts package with:

npm install -g react-scripts

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact