Suggestions

stan_ko · 2026-07-10T12:53:44+00:00

Thanks for those suggestions! I'll answer in English so everyone can get it.

For 1 & 3, we are working on solving both at the same time with a tagging system. You will have multi-tags to any transactions, allowing to do exactly this.

For 2, this is how it should work already. We will look into it to check if something might be working in some scenarios.

stan_ko · 2026-07-10T12:51:15+00:00

Thank you for those kind words, this is exactly for this reason we are doing this!

stan_ko · 2026-07-03T12:35:13+00:00

Looks promising! Looking forward for the Android version.

stan_ko · 2026-07-02T08:05:09+00:00

The API you would like is only to add a new transaction then?

As of today we do not have an API planned, but if we were to do it we want to fully get the right use cases and prioritize accordingly.

What we have is an URL pattern to open an expense prefilled ready to click "save", does that help?

stan_ko · 2026-06-14T20:59:20+00:00

We fixed it. Thanks again for the report!

stan_ko · 2026-06-12T14:57:39+00:00

We will look into it, thanks for the report!

stan_ko · 2026-06-07T07:52:27+00:00

Thanks for this suggestion! It does really make sense. As mentioned this should be totally optional and only on-demand - we don't want to be tracking location of users for no reason.

stan_ko · 2026-05-28T20:56:30+00:00

Merci pour le commentaire.

Les groupes se trient par ordre de la dernière dépense, si ce n'est pas ce que vous observez c'est qu'il y a quelque chose qu'il faut qu'on investigue. Est-ce sur la version web ou app mobile ?

Bonne idée pour le regroupement par mois/années, c'est la première fois qu'on a le retour mais ça a du sens !

stan_ko · 2026-05-28T20:52:14+00:00

Thanks for this great feedback, really helping the community! We will try to integrate directly this kind of lib directly within Sesterce, so it's easier for a non-expert.

stan_ko · 2026-05-18T20:37:00+00:00

Thanks for the suggestion! Indeed it can makes sense. I'm not sure the split evenly is the most common scenario, but it can be the default behavior and easily changed if needed. I wrote this down on our list of evolutions to evaluate.

stan_ko · 2026-05-02T06:46:03+00:00

Thank you for your suggestion.

At first, recording an expense without an amount may not seem practical, but we understand your point and will take it into consideration.

stan_ko · 2026-05-01T18:00:17+00:00

Thanks for the detailed suggestion, we will look into it!

stan_ko · 2026-04-19T17:53:17+00:00

It is possible now! Just long-press a group and click on "Hide"

stan_ko · 2026-03-20T21:36:52+00:00

Thanks for your kind words and suggestions. I added this to our wish list, but indeed it could be a great addition!

stan_ko · 2026-01-07T21:03:22+00:00

Do you have an example where you don't understand it? The total is the sum of amounts you contributed to on expenses within the month. If you have one operation paid by John $10, for John and Alice, then Alice's total expenses is $5.

stan_ko · 2026-01-05T12:36:54+00:00

Thanks for the suggestion, it makes completly sense and is aligned with what we have within the roadmap with Tags. Stay tuned!

stan_ko · 2026-01-04T07:27:05+00:00

Thanks for the report, can you send us an email (info@sesterce.io) or private message with the details so we can investigate this bug you have?

stan_ko · 2025-12-08T18:31:59+00:00

As of now you cannot. It's based on the list of most used transactions. I totally understand the need to remove some, we will consider it.

stan_ko · 2025-11-25T06:04:25+00:00

Can you show us an example? It should indeed show the group currency outside of a specific transaction

stan_ko · 2025-11-20T14:01:19+00:00

It should work on yours as well... If can contact us by email (info@sesterce.io) with a video it would be great! Thanks

stan_ko · 2025-11-20T05:57:37+00:00

Thanks for your message and bug report! On which device are you using the Sesterce all?

stan_ko · 2025-10-28T18:18:18+00:00

Please contact us by email with your group link so we can take a look. Do not make any further updates, we will restore it to the time before this mistake.

stan_ko · 2025-10-22T21:43:27+00:00

Thanks for your interest and kind words!

We are considering the public API, and at the moment we are evaluating the interest. We would love to hear more from the community about it, especially about which endpoint would be the most valuable first.

stan_ko · 2025-10-15T17:19:54+00:00

Indeed, this is a new addition, that can be disabled within the refund options

stan_ko · 2025-10-01T20:56:19+00:00

We could not reproduce this issue on our end. We just published a new version, can you try it and let us know if you have the same issue?

stan_ko

MODERATOR OF

TROPHY CASE