774 karma · joined June 3, 2017
You can try out the accounting system here with no sign-up at https://demo.joincycle.co. You can join the waitlist to use it when we launch with business banking.
I have built the platform in Elixir, Phoenix, Inertia JS and React. I had launched it initially as workbill.co, as a standalone accounting platform, but later pivoted to this.
Unlike traditional accounting platforms we expose the ledger model directly which enables our customers to model complex transactions even when we do not have direct support for it.
Been working on this for a month, and it uses Elixir, Phoenix and InertiaJS with React.
I started Paper to bring the beancount + automated parsing with python stack to everyone. Double-entry is an objectively better way to manage your finances, when we build an automatic reconciliation engine that automatically categorizes the bank transactions we'll have the best personal finance tracker app.
India does have a decent open-banking system, used by https://fold.money
> Yes you can, it's called a split transaction. $1000 income: split into $700 to my savings and $300 to taxes.
Even though this would work, the money is still in your bank account, which makes your savings account balance to be reported wrong.
The goal is to have the major functionality of the platform tested automatically so we can be confident that new features don’t introduce new bugs.
My blog is a collection of txt files. Here's a post about why I wrote it in text files https://aswinmohan.me/only.txt, here is another post about Phoenix LiveView https://aswinmohan.me/superfast-liveview.txt
Since we can't add links to text files, they follow the markdown format of links [link](url) where you have to manually copy paste the URL in the URL bar. The text is hard wrapped at 80 chars, and no indentation is used since it messes up the look on mobile. I love it, what do you people think ? Yeah or neh ?
- Scaling Databases is hard, - It's easier to scale a stateless application server rather than a stateful database.
- SQL is still hard to maintain - Adding features using Postgres Functions means you have an additional language to maintain. The code might be spread across different migration files. Maintaining these functions long term has it's own issues.
I really liked your detailed write up on the publishing chain you have used, code is just text in it's essence and because of that programmers have access to superior tools for it's manipulation. But that power is hidden behind a steep learning curve. IndiePaper is just the collection of tools you have specified all integrated and wrapped up as a web app.
Regarding examples, I never thought this would blow up on HN, that's why it doesn't it even have an FAQ, I'm working on a new design that would bring published books of the platform front and center.
Technical books are and will be supported, even though technical authors have the know-how to setup up a publishing toolchain, most would love to write in a completely integrated platform. Since we control the entire editor, we can and will support code snippets, highlighting and comments by adding to the text-editor raw structure and processing it during typesetting phase.
IndiePaper was actually ideated with rich technical books from the start, features like code integration with Github were all thought of from the start. So IndiePaper will have first class support for technical books.
I still haven't decided on what input format I should be using, most authors are familiar with a WYSIWYG style editor, but technical authors are more inclined to markdown like formats.
Authors are more inclined to switch with the writing tools they already own, so I think multiple import options and a single editor representation would be better. Upload a bunch of files of asciidoc or markdown and get it published.
- Once the typesetting engine is finished you can export the books and sell on your preferred platform.
- Uploading each chapter would be finished when I move the editor page to a SPA. That way we can get a more stable editor and a better authoring experience.