fishsander

very cool! thanks for sharing!

had you ever designed a font prior to this? what's the process like?

Justin Kan & others tried this a few years ago with Whale (https://www.crunchbase.com/organization/whale-3)

Haha, thanks for your concern. I don't think you broke it all by yourself ;). Just upgraded the dynos, it's back up now!

That's great feedback, we'll add labels soon.

Thanks, just upgraded the dyno formation, it's back up now!

We thought that would be the best way to get people to try it :)

Do you see that each day is split up vertically in three parts? Each part resembles a part of the day, which you can click to add your priority. On desktop you can add your priorities directly in the overview.

Hey HN,

Creators here. We've been using this planning method for a while and decided to turn it into a product to see if it's helpful for others. I struggle with focus a lot, while Joris (other creator) struggled to prioritise the right things. We both use this method by planning our week ahead on Sunday or Monday, where we set 3 priorities per part of the day (morning, afternoon, evening). Often we keep a few "dayparts" open as a buffer if something comes up.

We built the planner using Meteor, React, Styled Components, Reach UI, react-beautiful-dnd and react-tiny-virtual-list.

I explained a bit more about how we turned this method into an app on Medium: https://medium.com/swlh/finding-clarity-and-focus-as-a-maker...

While we feel like the product is pretty much finished (we've been using it for months already), the hardest part is to explain the method to people. So we're specifically interested in feedback on that part.

They don't, although you can create invoices in the dashboard if you know who your customer is.

Alternatively, I built https://checkoutpage.co to create hosted payment pages for Stripe that are accessible by url, similar to Razorpay's payment links.

That's correct. When I said developers, I primarily front-end developers who don't write backend code. People who are able to build static websites and usually make them interactive with plugins, extensions and services.

I need to think how I can make Checkout Page interesting for full stack/backend developers. It would then mostly be a time saver, for which the fee is indeed too high.

What kind of pricing structure do you think would work well for a developer like you?

Awesome! I am considering subscriptions as well but it is further up on the roadmap.

Thanks! The functionality of Stripe Checkout is similar, although when using it you still need to process the payment on your own server. Checkout Page does that for you.

I made Checkout Page to create a way to use Stripe for both developers and non-developers.

Checkout Page lets you really easily create one page sites where people can pay you on. The use cases are endless, but think of selling courses, ebooks, physical products, advertisement spots or getting invoices paid.

With future developments I aim to make Checkout Page an unopinionated way to sell online. On the roadmap are things like Zapier integration, dynamic pricing, webhooks and dynamic return URL parameters.

I would love to hear your feedback!

Their staging and development branches are both 375 commits ahead of master.

We started working on Wordeys this summer (on a cool hackweekend at a farm), after we felt like there was a gap between learning the basics of languages and mastering languages. On top of that, when using existing language learning apps we always feel some sort of annoyance; it’s really helpful at first, but then it gets boring, time consuming and irrelevant.

That’s why we made a tool that lets people save relevant words, grammar and vocabulary into lists, which can be practised (like flashcards, but with soft spell checks). This enables people to only spend time and effort on the stuff they need.

By focusing on a minimal, clear UI and integrating Google Translate we make it possible to build these lists really quick.

We would love to hear everyones thoughts on this!