New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make companion mobile apps (iOS and Android) #72

Open
iffy opened this Issue Apr 25, 2018 · 7 comments

Comments

Projects
None yet
5 participants
@iffy
Contributor

iffy commented Apr 25, 2018

After v1.0.0 of the desktop app is released, I will begin work on a mobile app.

@iffy

This comment has been minimized.

Contributor

iffy commented Apr 25, 2018

@iffy iffy added this to Future consideration in Buckets Work Apr 25, 2018

@kianrafiee

This comment has been minimized.

kianrafiee commented Jul 27, 2018

Awesome work on this project. Once you have an iOS app, I will switch over to buckets.

@Limezy

This comment has been minimized.

Limezy commented Dec 11, 2018

Hi Matt, any ETA for that one ?
If you need any beta (or alpha) testers I'm in !

@AAverin

This comment has been minimized.

AAverin commented Dec 12, 2018

@iffy If you can come up with some tasks, maybe community would be able to help with apps development?
I am trying to come up with a workaround, maybe find some app that would let me track transactions and take pictures of receipts, so I could sync them with the app later.
But the point is – apps are essential, even if they only can track transactions

Even better if you could collaborate with some existing apps.
For example, this one is very simple, just for tracking, and exports to CSV: https://play.google.com/store/apps/details?id=money.expense.budget.wallet.manager.track.finance.tracker&hl=en

@iffy

This comment has been minimized.

Contributor

iffy commented Dec 12, 2018

@AAverin thanks for your comment on this. After playing with various frameworks and even looking at developing the apps natively, I think I've finally settled on how I want to approach the apps (webview at first, with the possibility of going native later). I should blog about my research and findings.

And yes, the first versions of the apps will likely be limited to apps that "only can track transactions."

That said, I'm not opposed to anyone that wants to make or alter an existing app to work with Buckets. I would even be up for documenting and publishing the API I plan to use to sync the desktop and mobile Buckets apps. And I could also possibly (no promises yet) release that API even before the mobile apps are done.

@AAverin

This comment has been minimized.

AAverin commented Dec 12, 2018

@iffy I am fullstack mobile dev, I do both Android and iOS apps natively + backends in Java and Node

With my experience, for a small startup without huge money on the table, I would recommend starting with PWAs, adapting existing javascript codebase.

I wouldn't recommend going to React.Native – efforts there are not much less than building 2 native apps, even tough it might seem that it's faster, and there are lots of issues with maintenance and hiring people to support React.Native – no native devs are eager to develop with this tech stack.

The ultimate goal would be, of course, to have proper native app with full functionality. It's usually quite expensive to build and doesn't result in direct money, but rather adds to customer happiness and brand love.

For you particular case, the trickiest part would be synchronisation. With database for the budget beings some kind of file, it would be challenging to update that file from the mobile app – probably something like Google.Drive or Dropbox could be of help. Still, I am using an app for passwords that works exactly like that – there is a desktop app that saves into a file, file can be put to Google.Drive and app can connect to Google.Drive and modify same file.
This is the path I would recommend for you.

Regarding adaptation of existing apps – I think if you will offer tooling and contact some developers, they might get interested.
I have tried nYNAB and was trying to find cheaper alternative, was very surprised to see Buckets and so far I like it, except for the lack of mobile app =)

Anyways, I think initiative for apps should go from your side, like, contacting developers and offering them something. Also, I wouldn't mind to pay for mobile app support, considering that the price for the desktop app itself is very low and, having a few of my own projects I try to sell, I can say that 29$ is not enough to cover for your time your family losses.

@sanecito

This comment has been minimized.

sanecito commented Dec 13, 2018

I thought I'd chime in as well as someone who recently bought Buckets to help fund mobile development which is the only thing holding me back from switching from YNAB4: I too would be willing to contribute to a crowdfunding effort to help accelerate mobile development. I'd also be especially willing to contribute money to any efforts to port the existing GNU/Linux version to work well on GNOME+KDE for the mobile form factor that is Librem5 and other GNU/Linux phones when they launch in April.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment