Since
@Alex doesn't care about us anymore, I'm taking over Financier. We thank him for his services, and wish him well in his new position as 'janitor'. With him out of the way, we can start making progress again. First order of business: a functional mobile application.
I haven't been able to break into the web server he set up, so I will be hosting a new mobile website on my own server. He left the door wide open on the database, so we should be able to access our data easily enough. I will be using a newer version of Angular to build the site, so pretty much all of his code is totally useless.
So far, the basic login/logout logic is working. Next up is figuring out how to sync data to provide something to work with. I plan to start simple with account/category balance views, and a simple mobile transaction entry form. I'm going to hold off on posting a link until I have something that's somewhat functional and stable.
I think the future of Financier will be bright under this new
regime ownership. I look forward to the mandatory loyalty that you will all bestow upon the company.
Disclaimer: Do not take this post seriously. ;)
I bow down to my new financial overlord! asromzek! asromzek! asromzek!
Waiting for the ban in 3... 2... 1...
@asromzek I know your post is tongue-in-cheek, but to members that haven't been around as long as some of us, it comes across as not so nice to
@Alex. Maybe you should edit the post and add some sort of emoji to soften the blow. Just my two cents worth.
Done. ;)
I thought it was already assumed from the signature! :P
Now we have someone new to aim the pitchforks at!
In all serious, I respect both of your efforts even if I haven't made the switch yet.
Aw, I was hoping this is for real.
I can't wait for purple FinaNAB. :parrot:
Status Update: Mild successes edition.
Not much new to report, other than that I'm wading through the pouchdb API documentation, and studying how
@Alex built Financier around it. Very cool stuff. I managed to create a local database, and next up is attempting to sync with the real deal.
Free time has been in short supply this week, so I'm handing control of the company back to Alex.
Quote from: asromzek on May 03, 2017, 04:20:57 PM
Status Update: Mild successes edition.
Not much new to report, other than that I'm wading through the pouchdb API documentation, and studying how @Alex built Financier around it. Very cool stuff. I managed to create a local database, and next up is attempting to sync with the real deal.
Free time has been in short supply this week, so I'm handing control of the company back to Alex.
Good.
At this rate, we'll have feature parity with YNAB4 in no time.
(http://i.imgur.com/Lq2XPZG.png)
Status Update: Quack quack edition.
All may seem quiet now, but about 4,000 lines of new code have been added to the mobile app since Friday afternoon. Most of that is based off the core Financier code to ensure that the math and calculations will be the same between clients. I'd like to say I'm doing something revolutionary, but in reality I'm just reinventing the wheel... a couple hundred times over.
The good news is that the mobile app has potential for full functionality. The 3 main things that I plan to implement first are account balance views, category balance views, and transaction entry. After that I'll consider the other stuff like editing budget values, editing transactions, notes, reordering things, etc.
The bad news is that
@Alex could change things at any time, so I'll have to stay vigilant to make sure the two clients don't fight with each other, and to propagate any bug fixes and new features.
I don't have a good estimation on when the first basic functions will be ready, but things are moving along rapidly behind the scenes. Im like a calm looking duck, kicking under the water...
Happy to alpha / beta test it out for you once you get a little closer. I have a pretty good knack of finding bugs and I'm a daily user of Financier :)
I just pushed up a few more changes which should make logging in and out is a little more stable. The initial sync has been a challenge to wrap my head around, mostly because I've departed from copying Alex's code, and doing things my own way. The core math stuff was pretty straight forward, but a lot of the Angular 1 UI/UX stuff doesn't really apply to what I'm working with. I'm also not a CSS expert, so I'm taking the easy route by using bootstrap to theme the thing. ;)
Again, the link: https://fmobile.asromzek.com (https://fmobile.asromzek.com)
Quote from: asromzek on May 11, 2017, 08:40:40 PM
Again, the link: https://fmobile.asromzek.com (https://fmobile.asromzek.com)
Thanks :)
Alright, can you guys see account balances, and are they correct?
Edit: Account sort order is not implemented yet.
Quote from: asromzek on May 12, 2017, 03:31:04 PM
Alright, can you guys see account balances, and are they correct?
Edit: Account sort order is not implemented yet.
Yup, can see account balances and they appear to be correct. Good job!!
One step at a time...
The app routing structure is getting reworked tonight.
Another minor update... hashing out some of the navigation stuff. The accounts should show up in the correct sort order as well now.
@asromzek All correct and in order.
Nice work!
Quote from: asromzek on May 12, 2017, 04:59:16 PM
Another minor update... hashing out some of the navigation stuff. The accounts should show up in the correct sort order as well now.
Yep looking good, all accounts displaying correct balance and in order. :)
For now the data will be static after loading (numbers won't update as sync changes roll in). You'll have to refresh to see any new data that was synced, which is the simplest way to get things up and running.
I plan make the whole thing dynamic so the numbers update in real time as sync changes are detected, but it's looking like I'll have to go back and refactor a bunch of the internal code that was
copied from inspired by
@Alex. I'm using a totally different event system, so it'll be fun to figure out how to wire up all of that stuff from scratch.
Today I discovered the "display as mobile" option in chrome dev tools, which renders the page in different phone screen sizes. That has been really handy for testing out different layouts. So far, things are looking good all the way down to iPhone 4.
Ran into a few snags last night, so I'm rewriting the data engine from scratch. No big deal. :)
I can extract a lot of the logic from what I already have, but I want to use typescript to its fullest potential (everything has a type!). I'm also building a comprehensive event structure that the front end can bind to for automatic change updates.
The budget and account structures are already complete. Transactions, categories, and payees are next. Then the fun part: month calculations.
It's going to take some time, but it should make building the front end a lot easier and straight forward.
Status Update: Worn out edition.
Still chipping away at things slowly behind the scenes, and dealing with some real life stuff this week. Hopefully I can ramp back up to full awesomeness by the end of the weekend.
Any news? :-X
Not a lot to report, unfortunately. The company I work for was hit by a computer virus a little over a week ago, and 110% of my time has been spent patching and cleaning computers around the clock. We're starting to see the light at the end of the tunnel, so hopefully I'll have my evenings and weekends back again soon. I'd much rather be developing web stuff than dealing with that mess.
"We have Windows XP machines scattered all over the place. We need all of those patched... Oh, only service pack 3 is patchable??"
...
"How about this one and the other 15 that are running Windows 2000?"
...
"Oh yeah, these Windows 95 machines are supposed to run for the next 10 years. What about those?"
.............
:o
After a turbulent summer, the gears are starting to grind again...
I've spent the last two days picking up where I left off. My wife has been complaining about not being able to enter transactions while on the go, so I'm targeting that first. That and the ability to check category balances. I threw out about 2/3 of the existing code after reading up and researching the Angular2/4 framework a little more, and determining that I had no idea what I was doing. We'll see how the next few weeks go.
Just a sneak peak of what's to come...
https://fmobile.asromzek.com/ (https://fmobile.asromzek.com/)
(Best viewed on your phone)
I tossed out 100% of the Angular 2/4 code and started over with a brand new Vue.js project on Sunday. Why? Because I'm an adult and I can do what I want.
There isn't much on the surface yet, but the sync mechanism and underlying data model are completely intact. I borrowed a good chunk of code from the main Financier project, so the math should be identical. I'm at the point where the rest of the coding will be from scratch and only loosely based on the main app. I'll upload the source code with an MIT license once I have a somewhat stable version ready to go.
Next on the list: Opening budgets and viewing account balances.
Alright, things are humming along smoothly. I decided to go all out with making the mobile app run offline just like the main app. I had to refactor a good chunk of the app to make that happen, but it's looking fairly solid now. Before doing anything further with data stuff I departed down the path of... color themes...
Hmm.. Color themes are by far the most critical portion. Make sure you get that right :-p
Quote from: jat255 on September 25, 2017, 11:33:40 AM
Hmm.. Color themes are by far the most critical portion. Make sure you get that right :-p
I wasn't about to write a single line of budgeting code until that was firmly in place and tested.
We're good to go now. :parrot:
FYI, the Gitlab issue tracking system is being used to keep track of features & bug fixes that are on the way, in process, or ready for deployment. Unfortunately, iOS is the only phone operating system in our household, so testing for other devices will be limited. Feedback from those with other phones is more than welcome.
Android user, happy to provide anything information you need.
Theming is working well.
Account balances don't have monetary symbol or formatting/mask.
Anything else you need?
Android 8.0.0
Chrome 61.0.3169.98
Quote from: Billy_McSkintos on September 25, 2017, 02:27:02 PM
Android user, happy to provide anything information you need.
Theming is working well.
Account balances don't have monetary symbol or formatting/mask.
Anything else you need?
Android 8.0.0
Chrome 61.0.3169.98
Just updated and released. (Version 0.2.2) ;)
Working well on Nexus 5x with chrome.
Hooorar! :D
v0.2.3 released: Login error message and warning modals for logging out & clearing local data.
v0.2.4 released: All accounts total. On/off/closed accounts totals. Reduced default text size across app in preparation for displaying transaction data.
Looking good!
Yea its looking really good.
I just spent 40 minutes making 22 themed favicons... :parrot:
v0.2.5 release: Themed favicons, because why not? A few other small bugfixes. The whiskey is kicking in, so I'm not going to dive into transactions tonight.
No "official" version tonight, but I have transaction lists underway, and pushed what I have so far. Ran into some scrolling issues when loading a large list, and spent a few hours figuring out an infinite loading solution. Don't worry about the formatting, it's far from what the final version will look like.
Edit: I just noticed that it's still loading the full list of transactions without loading chunks when scrolling like it should. Eh, I'll figure that out tomorrow.
Edit 2: Fixed. I just needed a couple hours of sleep. :)
Its looking great, i'm so impressed!
Loading/Syncing speed is good.
Scrolling/loading functions well.
I like the size of the fonts and hence the amount of information I can see.
Thank you for all the hard work you are putting in.
Google Pixel XL, Android 8.0.0
Chrome 61.0.03163.98
Is there any way that I could see this "Gem" in action ?
Quote from: keyboard on September 27, 2017, 09:54:14 AM
Is there any way that I could see this "Gem" in action ?
Load up https://fmobile.asromzek.com in your phone's browser.
FYI, I broke some stuff like the app not jumping to the main page after successfully logging in. If you notice little things like that, you can be sure that I probably have as well.
Hi
Do I need a login name and password ?
At this time, yes. You need a Financier login account, and the mobile app syncs with the data entered in the your main Financier budget. If you don't have a paid account, I think it will work with a trial account for 7 days.
@Alex can confirm that I'm correct in saying that.
I have an account, never thought of using it for the login ....... Boy do I feel silly now . :) :) :)
I was slammed with some real world stuff today, but I had enough time to refine the transactions view a little bit. I didn't get to testing the cleared/uncleared/reconciled icon under the date like I wanted to. I may abandon that idea and try cramming it on the right side of the amount. So far it looks good on my iPhone 6s, but I think the category and memo may have overlap issues on narrow phones like the iPhone 4.
Wow it's looking really good, its even doing the live sync. :)
Quote from: ottyacat on September 28, 2017, 12:28:05 AM
Wow it's looking really good, its even doing the live sync. :)
I made sure to bake that into everything from the start. Fast live syncing is one of Financier’s best features.
v0.3.0 released: Initial transaction views implemented (still incomplete). Smooth touch scrolling was implemented for all lists. Budget name is displayed in header after opening.
The smooth scrolling appears to be working well on iPhone, but I don't have a way to test with Android. The intent is to have the list keep scrolling for a second after swiping up or down, slowing down gradually until it stops. I also need to get the scroll to top when clicking the top status bar working. I know there's a way to do that...
There's still a bug where the app doesn't jump to the home screen after successfully logging in.
v0.3.1 released: Fixed the redirect to home after logging in bug.
Yep smooth scrolling appears to work on Android 8.After the first couple of swipes (to get the infinite scroll data) scrolling back up the list scrolls really fast and then slows down after about a second until it stops.
It’s a little clunkier than I like. Some refinement is on the way. The little loading spinner isn’t necessary, and will be removed as soon as I solve a few odd issues.
v0.3.2 released: The loading spinner stays. Transaction loading chunk size increased to 50 at a time. If you've scrolled down the transaction list, clicking the Cleared/Uncleared/Working balances bar will scroll back to the top. (actually, it resets and reloads the transaction list)
v0.3.3 released: Transaction cleared/uncleared/reconciled icons added.
v0.3.4 release: Fixed a few icon/image things under the hood, and attempted to implement offline mode. If you load the app up, close the browser, put your phone in airplane mode, and then re-open... the app should load up in offline mode. It appears to be working on my iPhone, and it's supposed to work on Android. Test away!
Android: Yes, but it only worked for me when the browser window was open and I switched to airplane mode. If I closed the browser window, switched on airplane mode, then loaded fmobile, it wouldn't load. A function of Android perhaps?
I need to get my hands on a phone with android to test.. I just dropped the offline library in and enabled it, so I’ll spend some time to see if I missed some settings.
Yea same thing for me, it loads the last page i viewed but if you click on anything it then says you are offline connect to the internet etc. etc.
v0.3.5 released: Clicking on a transaction will display split information if available, as well as the Edit/Remove transaction buttons. The don't do anything yet, but finalizing the layout was nearly the last step before building the transaction editor. Almost there...
Offline mode is going on the back burner for now. I'll revisit it when the app is a little more complete.
Edit: The transaction editor is probably the most complicated thing to figure out since it should provide auto complete for payees and categories. Building splits will also be fun. And I just noticed (because I failed to test for it) that split transaction information does not automatically update when they should through syncing. I'll fix that when I'm not dead tired.
Split updating is fixed, except for some odd behavior when a transfer to an on budget account is added as one of the splits. The split and target account don’t update with the transfer info until you refresh the app. I’ll handle that later. On to the transaction editor...
:parrot:
Awesome! Thank you for all your work!
Transaction entry/editing is well underway, and it's a beast to figure out. My compliments to Alex for making it looks easy. Most of the day was spent mocking up layouts and conceptualizing how things should flow. Connecting the dots is going to take some mental horsepower...
I may start with basic transaction entry, then transfers, and wrap up with tackling the complexity of splits.
Quote from: asromzek on October 01, 2017, 08:06:29 PM
I may start with basic transaction entry, then transfers, and wrap up with tackling the complexity of splits.
Sounds like a plan :). Believe it or not i enter transactions quite often on my phone in native Financier... Needless to say its painful.
#exciting
v0.3.6 released: Initial transaction editor is put together. Clearing/unclearing and changing flag colors for existing transactions is working, mostly as a proof of concept. Changing date, amount, payee, category, and memo will each have their own special editor which will be added one by one. Clicking the corresponding section will open up the editor for each. Once all of the editors are working for existing transactions, the ability to create new transactions will fall into place.
Edit: I forgot to mention that a significant transaction list syncing bug was fixed, after fighting with code for 3 hours and discovering a simple half dozen line change that made things magically work.
The weekend was busier than I expected so this all you get. Deal with it. 8)
Public service announcement: Back up your budget(s) regularly if you're testing the mobile app. Everything is tested thoroughly before releasing, but I cannot guarantee that a bug won't slip through resulting in a corrupted budget file. I managed to seriously break one of my staging budgets while working on the transaction date calendar. It was an obvious mistake made while tearing up some shaky code, but that would not have been fun to deal with on out in the wild.
Again, I'll do my absolute best to validate everything before releasing, but it's better to be safe than sorry. :)
How do I back up my budget?
There's a little gear icon in the main Financier app that contains backup and export options. If you backup your database to a file, you can restore it at a later date. I stole this image from the Financier blog.
v0.3.7 released: Date and memo editing have been added to the transaction editor.
v0.3.8 released: Fixed splits list not updating when transaction list changed during sync.
Next up is amount editing, payee editing, and finally category editing which may take as much effort as all of the other editors combined. This is mostly due to splits since each one as its own payee, category, and amount. I should be able to reuse those 3 editors when building a split, so it may not be as painful as I thought.
Working well so far :parrot:
v0.3.9 released: Transaction amount editor added. There's definitely room for improvement on this one, so feedback is welcome.
v0.3.10 released: Revamped transaction amount editor layout. Added inflow/outflow buttons, change "+/-" button to clear button, and change text on "Delete" button to an arrow.
Yea nice! That looking pretty swish now. Easy to use.
Just some eye twitching button alignment to remedy... ;)
I know it's really early days, too early for requests but is there any chance you will implement some form of option to select the date format down the track. Us Aussies struggle with the US date format.
Absolutely. Date format and translations will happen as soon as the app is a little more complete. Actually, I may tackle date formats sooner than later since that’s probably not too difficult.
Even I don’t like the US date format. As an engineer the only acceptable time stamp format is 2017-10-04 23:09:30.263
And that’s not even correct since it’s local time.
I didn’t version it, but I pushed out a few very minor layout and style tweaks. Mostly button spacing and colors.
I imagine the payee editor to be a textbox at the top, with the full list of alphabetized payees below it. As you type in the textbox it will narrow down or filter the list. Clicking a payee in the list will copy its name to the textbox. Typing a new payee will cause it to be created once the transaction is saved.
Should be simple enough.
Well, after doing some detailed testing this morning, I found a significant bug. If you used the mobile app to change the amount for a transfer, the transaction amount on the other end of the transfer would not update. This was due to a chunk of logic missing that should have come over from the main app, and required a major overhaul of the transaction editor :-\. The bad news is if you edited any transfers with the mobile app, you should check both ends of those transfers with the main app and fix their values (fixing one end will work). The good news is it looks like that bug is fixed, payee editing was added along the way, and the stage is set for category editing, finally.
With all of that said, I highly recommend backing up your budget if you continue to test the mobile app, preferably before you make any changes (obviously).
0.3.11 released: Overhauled transaction editor and implemented payee management.
I should also mention that the Transaction editor is missing a few protections that should stop you if you’re trying to do edit some things that you’re not supposed to. It’s possible to get a transaction in a stuck state that requires fixing on the main app. Those protections will be enabled when the category editor is finalized.
Unfortunately, nothing new to report so far this week. A busy weekend turned into a busy week. I really want to get category editing up and running, since that's the last piece of the puzzle for mobile transaction entry. This evening is looking rainy and drab, so maybe I can avoid the outdoors and get some code written.
Thanks for the update, let's hope for a rainy day :p
Looks like we have some coding weather coming up this weekend...
I made a little progress last night, and ended up getting derailed by a bottle of wine. We're clean out of beverages, so productivity should be improved this evening.
asromzek
You re a good man ..... We are very fortunate to have you here....
Ron
We're fortunate that
@Alex built a solid platform to play with. I'm really not doing much more than rearranging a lot of the code he wrote, and wrapping it with a new coat of paint. Well, it's also a bit like trying to cram a Corvette engine into a Chevette. There's a lot of data to display, and only so much real estate on a phone screen. I tried to roll things my own way a few times, and realized very quickly a lot of the core Financier code was designed quite a bit better. If it ain't broke...
As far as the current state of the mobile app, category editing is coming along nicely. Income for this month, and next month are easy to set, and single category selection is currently in the works. The split editor is going to take a little more thought, so I might wrap up the easy stuff and push it out before diving into that. The payee selector also needs a little polishing, but I may get to that after the category editor is 100% complete.
The icing on the cake will be adding that shiny new "Add New Transaction" button. :parrot:
Alright, it’s game time...
Disclaimer: As mentioned before, it is highly recommended that you backup your budget before testing the new mobile app features. The following version contains a number of new goodies, and there are still quite a few rough edges. Keep your bandaids nearby.
v0.3.12 released: Removed offline mode stuff for now, since it was causing headaches during debugging. Updated payee selection list. Added basic category editing (no splits, yet). Creating new transactions and removing existing ones are now enabled. There is no confirmation on transaction removal, so be careful with that. These features may still be a little shaky, so use caution and report any issues you may see.
I recommend avoiding anything having to do with splits for now, and that includes editing existing split transactions. You’ll simple wipe out the splits and not be able to put them back on mobile. Income for this and next month, and single category selection appears to be working as expected.
There are a number of UI/UX things that I will be cleaning up (like payee search being broken). I’m mainly concerned about transaction entry not working, currupted data, or syncing issues. So, have fun, and good luck...
Edit: The payee search bug was easy fix, so I pushed that without updating the version.
v0.3.13 released: Email address is no longer case sensitive when logging in. Payee search works correctly when adding a new transaction. The category editor is hidden when editing a transaction for an off budget account. "New Transaction" button was rename to "Add Transaction", and a small plus icon was added.
OMG this is so amazing, i entered a transaction from the shop whilst waiting for a coffee. #budgetingnerd
Last night my wife loaded up the site and had trouble entering a transaction. She clicked Save, the syncing indicator spun a bit, and the transaction didn't show up in the list. It worked fine after refreshing the page. If you see anything like that happen, let me know. I hope it was a fluke, but I'll be trying to find an explanation.
I have also noticed a small glitch when adding/editing a bunch of transactions in the mobile app, and then loading the main app. The numbers for cleared, uncleared, and working balances are off by a little bit in the main app, and refreshing the page fixes it. This could be a bug in the main app code since the mobile app appears to be syncing the data correctly. This morning the cleared balance was off by $0.72 for one of my accounts when loading the main app and syncing a few transactions that I updated with the mobile app. I'll be looking into that as well.
Financier was down for several hours yesterday. It only came good. Sometime early last night my time. I noticed it back up approx 10 hours ago. Perhaps that was related?
Financier appeared to be up when I was testing, but it could have been related. I got a notification last night that Digital Ocean was doing network maintenance on the NY servers, where I have the mobile app hosted. I'll be keeping an eye on it since I haven't been able to recreate any of those issues today.
I'm not going to have much time tonight to do anything, so here's a small update to kick off the weekend.
v0.3.14 released: Added transaction removal confirmation. It takes two clicks to remove a transaction. Exciting stuff...
Monday morning update: Nothing to report.
Spent the weekend splitting firewood for my in-laws, and recovered on the couch last night with a beverage. I did spend a couple of hours throughout the weekend attempting to mock up some split editor layouts, and ended up scrapping everything. Figuring out a clean design for that has been a challenge, so that's the top goal for this week. I may polish up a few things and push them out along the way, so it doesn't look like I'm slacking off completely.
Tuesday
morning afternoon update: Split transaction editing is 90% complete.
There are a few nagging issues left regarding splits that contain transfers, and that should be remedied tonight. After that and a little more UI/UX polishing, it should be ready to release. Creating splits is fairly straightforward, and editing existing splits is a bit more complicated, especially when transfers are involved. Adding, updating, or deleting a transfer on the other end when a split is edited has a few holes in it, and I will not release the split editor until all of that has been fixed and thoroughly tested. I also have not tested splits that contain income, that's now on the list.
There is still some mild weirdness with transaction entry from time to time, where transactions don't save correctly, and simply reloading the web app jars it into working again. I noticed it on my phone, as well as Chrome on my computer, and there were no error messages in the console. That will be fun to resolve, if it's possible to do so.
And I found one actual (very minor) bug in the main Financier app where payees are not removed when a split is removed, and that split contains the last reference to the payee. I noticed that occurring the mobile app, and tested the main app to see if worked the same: confirmed. I'll let
@Alex fix that one... ;)
Wednesday Thursday update: This week has not been good for side project development. A little progress was made, but things are not stable enough to release, yet. Just keep swimming...
I've been away for a while, so i was very pleasantly surprized at all the developments. I wanted to add my thank yous to you Asromzek, for a heck of an effort. I had lost enough hope that I was actually thinking of signing up for nYNAB. This is a game-changer. Cheers to you, my good man. :parrot:
I too was thinking about going to nYNAB as Financier is unusable for me without mobile. But coming back here after several months away and I'm blown away by the progress Asromzek has made--really great!
Maybe this has already been answered, but are you thinking you will keep hosting the mobile on your personal site going forward? Just curious.
The last week has been tough due to work and family issues, so I haven't been able to wrap up the transaction editor as quickly as planned. I'll be putting a push on to knock that out this week, as long as nothing else pops up.
I'm not sure what to do with the hosting stuff. I already had asromzek.com registered, so I simply created a sub-domain and stuck it there. I may register a separate domain once the app is closer to being complete.
Quote from: asromzek on October 24, 2017, 10:49:35 AM
I may register a separate domain once the app is closer to being complete.
Can
@Alex help with financier.io?
Yea that would be nice, mobile.financier.io or m.financier.io or something like that, all in one place as far as the domain goes.
I'm usually not one to complain, but this week is just the worst. Too many real world issues to get anything fun done. The only thing I have to report is that I managed to make 3 dozen (a full gallon) of pickled eggs for deer camp, so I have that going for me, which is nice.
The last two week have been rough, so development has been crawling along. Finally got a chance to play around tonight, and I think I have a somewhat stable release ready.
As usual, you might want to back up your budget before testing the mobile app.
v0.3.15 released: The split transaction editor is ready to go. However, there's a bug that I have not been able to crush. When adding a split that contains a transfer, the transaction on the other end of the transfer is corrupted. The transaction is not correctly linked to the split on the other end of the transfer, which causes some display issues, and allows you to incorrectly delete the transfer. Refreshing the page fixes the issue, but I am absolutely stumped as to why it refuses to work when creating the split. I recommend not entering or editing splits that contain transfers with the mobile app at this time. I'll keep looking into it, but I've had my fill with that particular issue for the time being.
There are a number of small issues that I plan to clean up, and feedback is definitely welcome. I'd like to make the transaction editor as smooth as possible before moving on to the budget view/editor.
Yes, I just spent my entire Saturday evening writing code, in case you were wondering. What else is there to do on a rainy Saturday evening?
v0.3.16 released: This is mostly a cleanup and bug fixing release. The biggest bug would occur when loading a direct link an account, and then entering a transaction, which would disappear into thin air. It turns out that the budget ID wasn't being loaded correctly when the account page was loaded, resulting in a transaction that was linked to nothing. Oops. A two line code change took care of that. The "x" clear icon now displays permanently in the memo editor. The transaction editor now only allows a single edit/remove menu to be open. Opening an edit/remove menu will close the menu for all other transactions in the list. Income for this/next now display properly when changing the date in the transaction editor. And finally, a simple change that should help with transaction entry: automatic category selection when selecting a payee. I thought this would be a challenge to implement, and a half dozen lines of code took care of it. Piece of cake.
Use the following feature with caution.
I did enable one more thing which seems to be a little buggy right now: phone "web app" compatibility. If you open the mobile site on your phone and save a shortcut to the home screen, the mobile site will startup and run like a mobile app (no browser stuff top and bottom). I have only been testing this on iPhone, but it should be Android compatible as well (maybe?). However, every now and then the app will open up and display a completely white page, and deleting the shortcut, clearing the browser cache, restarting the phone, etc. will not remedy the issue. And I just noticed that my iPhone requires me to log in every time I load the app, which means cookies or the cache isn't saving correctly. This may take a little more thought, but feed back from Android users would be helpful.
Well, the home screen app shortcut was forcing me to log in on every load, but now it's persisting. I may write up some instructions on how to set that up when I'm actually awake.
Edit: And it looks like there are a lot of issues with buttons missing and click events acting weird. It's probably a good idea to stick to the browser for now.
v0.3.17 released: Added cache busting library in an attempt to force reloading on iPhone home screen web apps. Running the app from a home screen shortcut on iOS seems to be really flaky, and this is a simple change to attempt forcing a reload when open the app. I'm having issues with the login persisting between opening/closing the app (in addition to a lot of other weird behavior), and it looks like it's simply the way it works with iOS and Safari. Maybe those with Android will have better luck.
Quote from: asromzek on November 05, 2017, 10:12:39 AMMaybe those with Android will have better luck.
Ahh this is great, much nicer than having a browser shortcut on the screen. So far so good! No weirdness, opens every time. I will give it a good smashing over the next day and let you know how I go. Android 8.0.0
Ok so used it a fair bit today, no issues at all. The auto-category after selecting a payee is a nice addition as well. Thanks for you hard work!
Quote from: ottyacat on November 06, 2017, 03:50:25 AM
The auto-category after selecting a payee is a nice addition as well.
That was already baked into the Financier code, and it only took a few lines of code to display the category after selecting the payee. I'm really not working hard, just wrapping a new UI around the core program. :)
By the way,
@ottyacat Your post just reminded me that date format selection needs to be added. That is now at the top of the list.
It just keeps getting better and better, thank you
@asromzek . BTW, home screen/webapp working great on Android 8.1.0
Quote from: Billy_McSkintos on November 06, 2017, 09:42:50 AM
It just keeps getting better and better, thank you @asromzek . BTW, home screen/webapp working great on Android 8.1.0
@Billy_McSkintos, are you using Chrome for full screen mode? I've gotten reports that full screen is not working well with Firefox. I need to get my hands on an Android device to do some testing.
Yes, using Chrome.
v0.3.18 released: Date format settings for
@ottyacat and friends. 3 simple formats to start, and I can add more if needed.
Quote from: asromzek on November 06, 2017, 04:37:56 PM
v0.3.18 released: Date format settings for @ottyacat and friends. 3 simple formats to start, and I can add more if needed.
Awesome thanks so much, working well dates now in dd/mm/yy format.
Actually I have noticed the date format settings are not saving through a browser close. The other settings are though such as theme! I have tried in the browser directly as well same thing as soon as i fully close and reopen it reverse to mm/dd/yy
@ottyacat, I know why it’s doing that without opening the code. I’ll fix that up after consuming the required levels of coffee.
Thank you for keeping the beating to a minimum. :P
v0.3.19 released: Fixed date format not saving between browser sessions.
Time to brag: I managed to fix this before getting out of bed by logging in to the web server with my phone, modifying the code, commiting to git, and building.
You are a good man "asromzek"............ He has my Vote !!!!!!
Quote from: asromzek on November 07, 2017, 06:35:12 AM
Time to brag: I managed to fix this before getting out of bed
Lol thats awesome :parrot:
v0.3.20 released: Mostly minor/cosmetic changes. The layout for the login page was improved, and the email textbox was set to type "email" which should bring up the appropriate keyboard on your phone. Added (fixed, actually) drop shadows to the memo and payee text boxes. Added the ability to clear the selected category. I'm not sure how this one slipped by, but there was no way to clear the category when editing an existing transaction that had one set. If a category is selected, the dropdown will now have an option at the end to "Clear Category". The dropdown text also displays "Category (None Selected)" when no category is selected. Should make a little more sense, I hope. And last, but not least... The "Amount Left" value when editing a split was changed to an absolute value, and the text was left green for positive, and red for negative. This one may be a little controversial, but my wife complained that having a negative value was confusing, so we can blame her if everyone else is confused.
I think this may be the final version before I dive into the budget view/editor. If anyone has any little issues to fix with the account/transaction stuff, now's the time to complain.
@asromzek Awesome work, thank you.
Not a complaint but a behavior modification. When adding a transaction or editing an existing one, I have used the back icon (Android) to cancel the edit/add transaction. This takes me back to the account list rather than the manifest of the account I was in. Is it possible to modify that behavior so that it cancels?
@Billy_McSkintos, good observation. When editing a transaction the account view is simply hidden, and the transaction editor is brought forward. It's all handled with a single view, and the URL doesn't change which causes the browser to take you back to the account list (the last URL visited). I will look into what it takes to override the browser back button to simply cancel if any editors are open.
I also noticed that when canceling a transaction edit, the account list scrolls all the way back to the top when the list is brought back forward instead of remembering where the list was scrolled to. I'm not sure if I can fix that, but I'll try.
Thank you but definitely not necessary to fix - just nice.
It’s a fairly straightforward concept, but complicated by the way the web components are structured. It’s on the list to improve. :)
v0.3.21 released: Clicking the browser back button while having any of the transaction editors open should simply cancel the editor instead of jumping back to the Accounts list. This appears to be working well in Safari on iOS and Chrome for Windows. It is
not working correctly in Chrome on my iPhone, and I think it's an issue with the browser. I'll do some more testing later. The transaction list scroll position is now retained when editing a transaction. And finally, all outdated Node.js packages have been updated, so hopefully that didn't break anything...
@Billy_McSkintos, let me know if the browser back button works as expected on Android.
Edit: One more vital piece of information... the loading spinner for the transaction list now reflects the selected color theme. :parrot:
@asromzek Yep, that is working. Thank you!
Monday the 13th update: I think have the budget view/editor mostly designed in my head. However, I'm not quite sure how to handle editing budget values. The simple way is to bind a textbox to each value like the main app does. You would be responsible for typing in numbers, decimal points, and maybe calculator characters, and the app would have to validate the input. While flexible, this could be tedious on a phone keyboard.
The other way is to pull up an amount editor like I made for transaction entry. This would provide better validation and might be easier for data entry, but it would make performing math functions a little more complicated since I would have to build an actual calculator with math operator buttons. I may start with the first method, and see how clunky it is before testing out a calculator input.
The next two weeks will be crazy due to beer deer hunting season and the Thanksgiving holiday, so development will be sporadic. Stay tuned.
Be Safe out there !!!!!
With YNAB's new ridiculous price increase, I decided to open up a nYNAB trial one more time. I was immediately turned off by the stupid way they deal with future-dated and scheduled transactions. It's beyond frustrating and I just can't get behind it. I'll likely keep using YNAB4 even if the mobile app eventually breaks.
How difficult would it be for someone to add scheduled transaction capabilities to Financier? That's the biggest hurdle I need to cross to switch over.
Quote from: Joel on November 15, 2017, 03:56:02 PMHow difficult would it be for someone to add scheduled transaction capabilities to Financier? That's the biggest hurdle I need to cross to switch over.
Whilst I am a full time Financier user, I too would love for this to be implemented. I know Alex was working on it at the time he stopped development. I wonder if the partial stuff is in the repo. Anyhoo if only I could code :(
I too tried another YNAB trial. It was not good. I've been using Financier exclusively for over a year now and am happy. I can export the data and wrangle reports in google sheets so most of the missing features I can work around.
We all know
@asromzek has done a spectacular job of the mobile app but that is built outside of Financier. I have seen a few people mention they are or have looked at the code but I wonder how many folks have a thorough enough understanding to contribute a solution?
Furthermore,
@asromzek has created a merge request for a small enahncement that
@Alex has yet to merge. So, even if someone can create a solution we are still at the mercy of Alex's work schedule to merge the code into the released version.
So, what to do? Are there enough avid Financier users capable and willing to contribute solutions? A community funded development slush/purchase from Alex fund?
I really don't mean to be negative or cynical, I feel like we are so close to an awesome product, i hate having it just beyond my reach...
I am planning to finish the mobile app (mostly just the budget view/editor is left), and then move on to adding some functionality to the main app if I can. If pull requests aren’t possible, then hosting a separate “enhanced†Financier may be possible. The sync mechanism is straight forward and flexible, so the sky’s the limit.
Quote from: asromzek on November 15, 2017, 10:21:18 PM
I am planning to finish the mobile app (mostly just the budget view/editor is left), and then move on to adding some functionality to the main app if I can. If pull requests aren’t possible, then hosting a separate “enhanced†Financier may be possible. The sync mechanism is straight forward and flexible, so the sky’s the limit.
Sounds really good, thanks again for all your efforts.
Huh, this topic was locked. I must have clicked that by accident on my phone. Looks like there’s interest gaining for further Financier development on reddit.
Monday update: Back to reality, and it's another very busy week. I did make a small amount of progress on the budget editor last week, but not enough to share, yet. This week should be a little more productive now that I'll be within range of electricity and a solid internet connection most of the time.
A little more progress made last night. Attached is a sneak preview of the budget view. It’s an early design, so the layout will be changing.
Love it so far !!!!!!!!
Looking good!
One of my favourite features of the YNAB app is the ability to pin categories to the top of the budget and then tap on them to create a transaction for that category.
Is that a possibility since you are early in the design/build?
Quote from: Billy_McSkintos on November 21, 2017, 10:01:48 AM
Looking good!
One of my favourite features of the YNAB app is the ability to pin categories to the top of the budget and then tap on them to create a transaction for that category.
Is that a possibility since you are early in the design/build?
The sky’s the limit. ;)
That made me think about another potential improvement. What does everyone think about having the transaction editor jump directly to the amount editor when adding a new transaction? That’s usually the first thing I click on.
Editing an existing transaction would work like it does now.
Quote from: asromzek on November 21, 2017, 12:48:31 PM
What does everyone think about having the transaction editor jump directly to the amount editor when adding a new transaction?
Yes
+1 !!!
+1, sneak peek is looking good.
Another sneak peek, now with more consistent color theming and the ability to collapse the budget info header.
v0.4.1 released: Why share screenshots when there's stuff for everyone to play with? The initial budget header view is mostly complete, although there will be a few more enhancements coming. The category budget view/editor is also still to come. I'm releasing mostly to give everyone a chance to give some feedback on the look & feel. In addition to that, when adding a new transaction the amount editor is brought up automatically, and then each subsequent editor is automatically opened after entering the previous information: Amount > Payee > Category > Memo. Give that a go, and let me know what you think.
Edit: I already see a (display) bug or two, so an "Under Construction" sign should be appropriate.
Really like it, especially the way the new transaction editor automatically opens each editor. This made entering transactions much easier.
Hggnh. That latest screenshot got my 'spider sense' tingling. I need tissues.
v0.4.2 released: The budget view now displays categories with budget, outflow, and balance values. The data is view-only at this point, but hopefully that adds a little value while you're out shopping.
There are quite a few things that need to be added to the budget view/editor, and the following is a short of things that I will be tackling first (in no particular order).
- Better indication that a previous, current, or a future month is selected.
- Tapping month display will take you to the current month.
- Budget view should remember the last month selected when leaving and reopening the view.
- Tapping a category name will trigger a new transaction editor for that category.
- Tapping a budget value will open the budget value editor (still designing that in my head).
- Tapping an outflow value will display a short list of transactions that make up the amount.
- Tapping the balance value will allow you to enable/disable the red arrow if the value is negative.
- The ability to pin categories to the top of the view. Likely a local setting, unique to the browser.
- Better value highlighting or hiding, to better match the behavior of the main app.
- Notes... These need to be added to more than the budget view.
As usual, feedback is welcome.
And here’s a screenshot.
FYI, I created a "mobile-dev" Slack channel: https://financierteam.slack.com/ (https://financierteam.slack.com/). If you have issues or suggestions, sometimes it's easier to chat and share screenshots.
v0.4.3/v0.4.4 released: Added green bubbles around positive budget balances, and dimmed budget and outflow values that are zero. Also removed currency symbols from budget, outflow, and balance values to conserve space, and because the main app does it.
v0.4.5 released: On a roll today... The budget view now shows a small red triangle in the top right when the current month is selected. The color theme for the budget view lightens when viewing previous months. And last but not least, clicking the selected month indicator (between the previous/next month buttons) jumps to the current month.
That's all you get out of me today...
I really need to spend the time to test this out... Good work
@asromzek!
@Joel, besides mobile transaction entry and scheduled transactions (I have a few ideas brewing for that), what are your other minimum requirements for retiring YNAB4?
Quote from: asromzek on November 27, 2017, 09:56:05 PM
@Joel, besides mobile transaction entry and scheduled transactions (I have a few ideas brewing for that), what are your other minimum requirements for retiring YNAB4?
I can’t recall. Life has been far too busy to give it much thought. Scheduled transactions are very important to me.
Payee rules are another frequently used feature from 4 that could really push me over the edge.
Can ofx files be imported? I think that was another important need.
There may be other items, but I can’t recall.
Wednesday update: Not much to report. Work has been a little more than crazy this week, and free time has been in short supply. I have been thinking a lot about the budget editor, and I need to do some maintenance on the transactions editor to allow you to set/change the account. This will be required when adding transactions from the budget view, and may also be used to move a transaction between accounts.
Besides that, are there any other issues with the budget view (layout, colors, etc.) that I should resolve before moving on to building the editor?
No issues that i can see or think of at the moment, its running really well!
Actually I just found one thing that could be tweaked a little better, if you enter a really long memo it doesn't wrap to the next line very well and makes it look really messy. Might be better to truncate it with some ... At the end or something like that.
Quote from: ottyacat on November 30, 2017, 03:38:58 AM
Actually I just found one thing that could be tweaked a little better, if you enter a really long memo it doesn't wrap to the next line very well and makes it look really messy. Might be better to truncate it with some ... At the end or something like that.
It’s funny you mention it, since that has annoyed me since day 1, and I forgot to add an issue on the Gitlab board to fix it.
The category and memo snap to opposite corners and are allowed to overlap. I need to revamp the transaction layout and implement a fancy grid which will provide the ability to limit the width of the memo if it runs into the category. I’ve been learning a lot abou CSS through the design of this thing, so there are a quite a few things that I will likely go back and make right.
asromzek
I gotta tell you that I get up every morning and the first thing I do, is check on what you have done the day before....
You have added much interest and hope and I am pretty sure that I can speak for everyone here to say that your effort, your time and your commitment are very much appreciated.
A Big Canadian Bear hug goes your way !!
Bravo, Bravo, Bravo
Your Canadian Friend
Ron
Quote from: keyboard on November 30, 2017, 10:05:09 AM
I gotta tell you that I get up every morning and the first thing I do, is check on what you have done the day before....
Lol i thought it was just me...
v0.4.6 released: Minor layout cleanup throughout the transaction editor. The category editor wraps amounts in red or green bubbles to match the budget view, although the text is a little bigger. The transaction editor does not jump to the category editor if editing an off budget transaction, or if the transaction is a transfer. Restructured a bunch of source files to pave the way for adding the ability to edit the account for a transaction. This will allow you to move transactions between accounts, and add new transaction from the budget view.
I was hoping to have the account editing done today, but some stuff came up this evening, so I'm releasing what I have done so far this weekend (not much).
Well, I managed to break free from the other commitments, and spent a few hours wrapping up some development tasks...
v0.4.7/v0.4.8 released: The account editor has been completed, making it possible to move transactions between accounts. A warning will be displayed when changing the account in the transaction editor. Category validation has also been enhanced, which will inhibit the submission of transactions without categories. If you do manage to enter a transaction without a required category (there are some obscure ways), then an appropriate "Category Required" message will be displayed in a variety locations. There are still further validation enhancements to be made in the transaction editor, especially in the split transaction editor (I haven't touched that lately). I'll may put that stuff on the back burner until budget editor is fully functional, which is coming up next.
Edit: Just fixed a bug that was causing the transaction editor to skip jumping to the category editor in certain cases.
Question: When pinning a category to the top of the budget in a special section (for easier access), should the category also be shown under its normal master category as well? In other words should pinned categories be displayed twice in the budget, once in the pinned area at the top, and also under its master category?
Quote from: asromzek on December 04, 2017, 01:46:17 PM
Question: When pinning a category to the top of the budget in a special section (for easier access), should the category also be shown under its normal master category as well? In other words should pinned categories be displayed twice in the budget, once in the pinned area at the top, and also under its master category?
That’s how 4 did it. I never used the pinned categories though. To be honest, I don’t even look at the category balances in my phone.
@Joel! You’re doing it wrong! ;)
Actually, I remember only having 3 categories pinned: Fuel, Groceries, and (shamefully) Fast Food. Although, pinning “Christmas Fund†temporarily was very useful for monitoring the category balance during a shopping spree, and made entering transactions really quick.
I don't mind either way, whatever is easiest but I could understand the need to see the sub categories grouped with their category heading. So, duplicated if you force me to pick.
Not a heavy user of that feature, occasionally i used to pin one or two. I think in both places would be good.
What-day-is-it? update: The budget view is getting an under-the-hood overhaul, which is a pain but necessary for adding editing capabilities. This mostly includes breaking a very large single component into many smaller components to make the code simpler, and more re-usable/scalable. The goal is to rip, tear, and refactor without breaking anything, essentially taking two steps back so we can go a mile forward.
This is the short list of items that I intend to implement after the budget view has been refactored. I can't guarantee that all features will make the cut, but I'm sure going to try...
- Budget value editor w/calculator.
- Outflow transaction summary.
- Red arrow toggle.
- "Add Transaction" shortcut button.
- "Pin to Top" for frequently used categories.
- Category reordering.
- Quick budget options.
- Move money tool. (this will be fun...)
- Category and budget cell notes.
Did I miss anything?
Quote from: asromzek on December 06, 2017, 05:13:02 PM
- Move money tool. (this will be fun...)
Don't waste your time! Let that be their thing.
I kinda like the "Move Money Tool" or something similar :) :) :) :)
Quote from: Joel on December 06, 2017, 10:26:08 PM
Quote from: asromzek on December 06, 2017, 05:13:02 PM
- Move money tool. (this will be fun...)
Don't waste your time! Let that be their thing.
That's one of the (few) features that I really liked in nYNAB, although I have a few ideas to make it work in a slightly different way. It's been a while, so some memory cells may need to be jump started. I consider this to be a luxury item, so some of the other features will likely be worked first.
Edit:
@Joel, there is one thing that can unequivocally be left as their thing: AoM.
Quote from: asromzek on December 06, 2017, 10:49:23 PM
Quote from: Joel on December 06, 2017, 10:26:08 PM
Quote from: asromzek on December 06, 2017, 05:13:02 PM
- Move money tool. (this will be fun...)
Don't waste your time! Let that be their thing.
That's one of the (few) features that I really liked in nYNAB, although I have a few ideas to make it work in a slightly different way. It's been a while, so some memory cells may need to be jump started. I consider this to be a luxury item, so some of the other features will likely be worked first.
Edit: @Joel, there is one thing that can unequivocally be left as their thing: AoM.
Fair enough. I haven’t used it enough to make much of an opinion on it, but I’m a CPA so I like adjusting amounts by using my ten key not mouse clicks.
QuoteDid I miss anything?
Is it possible to add a transaction from the (pinned) categories that automatically populates the category (perhaps more)?
I really only add transactions via mobile for groceries and restaurants.
Yup, that’s the exact purpose for having the Add Transaction button in the budget view.
Edit: Actually, that's how it will work for all categories in the budget view, not just the pinned ones. Pinning a category just makes it easy to locate the frequently used ones. It doesn't add any special functionality.
"Category and budget cell notes."
I tend to use alot .
"Category reordering."
Another keeper for me !!!
Well, it’s 9:15pm on a Friday evening, and I just got out of work.
yay. :-\
Even though we have a fair amount of stuff to do this weekend, I’m going to do my best to get some development done. For real. Seriously, I mean it.
v0.4.9 release: Added the ability enter transaction from the budget view. Tapping on category name will bring up a menu with an option to add a new transaction. The category will be auto-filled, and the account will also be auto-filled based on the last transaction for the selected category (if one exists). The budget was reorganized under the hood to make this work, and to prepare for additional budget editing functionality.
Unfortunately, this is all that I have been able to accomplish over the last week. The holiday season and work have been kicking me in the head. Looking forward to the winter lull... :P
Do you plan to eventually allow viewing of historical transactions within each category and within each account? To be honest, I use that capability of the mobile app more than most other features.
Quote from: Joel on December 14, 2017, 12:30:54 AM
Do you plan to eventually allow viewing of historical transactions within each category and within each account? To be honest, I use that capability of the mobile app more than most other features.
Yes, in fact I was considering that next since it should be relatively easy to implement.
When adding a transaction from the budget view, the account is auto-filled if possible based on the last transaction for the category. Should the payee auto-fill as well, with the transaction editor jumping to the payee selector after editing the amount? At first I didn’t like the idea of “guessing†the payee based on the last transaction for a category, but I’m starting to have second thoughts.
After using it a couple of times I tend to agree. At first I just expected it to do that and when it didn't I was like... Dang now I have to type lol... Not the end of the world but yea I think it would be nice at 90% of the time it's the same payee I find. Could always make it an option too I guess of people don't like it.
On second thought, how about a short list (maybe 3?) of the last or the most frequently used payees displayed on the payee editor, just above the main list of payees? For example, when adding a transaction for "Groceries", my short list of frequently used payees would display "Meijer", "Kroger", and "Aldi".
If you start typing in the payee search box that list would go away so you can better see the filtered list of payees below it.
This would apply also apply when adding transactions from the account view.
I like the most common idea.
Oh... yeah... development will be put on hold this evening due to a particular opening night movie viewing...
Quote from: asromzek on December 14, 2017, 09:29:37 AM
On second thought, how about a short list (maybe 3?) of the last or the most frequently used payees displayed on the payee editor, just above the main list of payees? For example, when adding a transaction for "Groceries", my short list of frequently used payees would display "Meijer", "Kroger", and "Aldi".
Yep definitely like this idea!
v0.4.10 released: A short (3 item max) frequently used payee list was added to the payee editor, only if you have a category selected during transaction entry. The list is sorted by the number of times a payee is used per category, and then by last date used if two payees have the same usage count. Once a payee is selected, the list is hidden.
It didn't take much to make this work, and I think it will speed up transaction entry significantly when adding them from the budget view. The algorithm to generate the list was a little clunky, and I didn't have a ton of time to test every possible scenario, so there may be a bug or two that got through. Yelling and screaming are encouraged if the app performs any less than perfectly.
The 3 most common payees for a category is brilliant! I love it!
Transaction summary for outflows is about 90% complete, but not quite ready to release. Just a few more loose ends to tie down and some layout formatting to polish up. The summary currently contains a list of normal transactions that pertain to a category for a given month, as well as transactions that contain splits for the category. It almost looks a little weird since the sum of the the listed transactions may not add up to the outflow total if a split transaction is present in the list. I may leave it like that since it makes it easy to edit the transactions from the list just like you can in the account view.
v0.4.11/v0.4.12 released: Transaction summary list for budget category outflows is a go. Tapping on an outflow amount will show a list of transactions that make up the outflow amount. As a bonus, full transaction editing is enabled for the summary list. The “Add Transaction†popup menu was removed and replaced with a better menu that matches the new outflow summary.
At the risk of sounding silly, how did you get the colors next to Meijer, Kroger and Aldi ?
Appreciate all the effort put forth !!
Quote from: keyboard on December 15, 2017, 04:00:35 PM
At the risk of sounding silly, how did you get the colors next to Meijer, Kroger and Aldi ?
Appreciate all the effort put forth !!
That’s the “flag†that you set when editing the transaction. The flag only applies to individual transactions, not the payee or category as a whole.
Learning stuff everyday !!!!!!! Many thanks !!
Can you add scheduled transactions to the desktop app? If so, that would be the last thing needed for me to make the jump!
Loving the development on this mobile app!
Quote from: Joel on December 16, 2017, 09:42:13 AM
Can you add scheduled transactions to the desktop app? If so, that would be the last thing needed for me to make the jump!
@Joel, everything I've done so far has been reinventing the wheel for a small screen. Adding functionality to the app as a whole will be a little more complicated, but not insurmountable. Database format modifications have to be done carefully to avoid causing conflict if
@Alex adds something on his end down the road.
Right now I see 3 potentially overlapping options:
- Attempt to build scheduled transactions into the main app, and submit a merge request for @Alex to approve. The benefit with this would be that he would not have to do the coding, but a crash-course in angularjs would be required on my end. My code would also have to pass the gauntlet of approval.
- Build scheduled transactions into the mobile app first. I have considered this heavily since I know my way around the mobile app code a lot better. I could figure out all of the mechanics under the hood, and then give @Alex the schematic to implement in the main app. Or, just let the mobile app handle scheduled transactions by itself...
- Build a small separate tool for managing scheduled transactions outside the main and mobile apps. I'm not sure if this would be any cleaner or easier than simply building the functionality into either app, but it's an option.
Scheduled transactions is the last piece of the puzzle for me as well, so it's going to happen someway/somehow.
Quote from: asromzek on December 16, 2017, 10:08:39 AM
Quote from: Joel on December 16, 2017, 09:42:13 AM
Can you add scheduled transactions to the desktop app? If so, that would be the last thing needed for me to make the jump!
@Joel, everything I've done so far has been reinventing the wheel for a small screen. Adding functionality to the app as a whole will be a little more complicated, but not insurmountable. Database format modifications have to be done carefully to avoid causing conflict if @Alex adds something on his end down the road.
Right now I see 3 potentially overlapping options:
- Attempt to build scheduled transactions into the main app, and submit a merge request for @Alex to approve. The benefit with this would be that he would not have to do the coding, but a crash-course in angularjs would be required on my end. My code would also have to pass the gauntlet of approval.
- Build scheduled transactions into the mobile app first. I have considered this heavily since I know my way around the mobile app code a lot better. I could figure out all of the mechanics under the hood, and then give @Alex the schematic to implement in the main app. Or, just let the mobile app handle scheduled transactions by itself...
- Build a small separate tool for managing scheduled transactions outside the main and mobile apps. I'm not sure if this would be any cleaner or easier than simply building the functionality into either app, but it's an option.
Scheduled transactions is the last piece of the puzzle for me as well, so it's going to happen someway/somehow.
Fantastic. With a newborn at home, I haven't had time to do any testing since it would require running both ynab4 and financier side-by-side with not enough time, but i think scheduled transactions would be enough for me to rip the bandaid off and switch completely!
v0.4.13 released: Added the ability to enable/disable the red arrow.
There are a few odd things that I noticed during implementation, but it appears to be inherent in the data model since the main app behaves the same way. I won't go into detail since you have to jump through a few hoops trip it up. Refreshing the app always "fixes the glitch", so I'm not too worried about it.
v0.4.14 released: Fixed outflow transaction summary in budget view not sorting by date/amount.
v0.4.15 released: The ability to pin categories to the top in a special master category has been added. Pinning a category will append it to the bottom of the pinned list, so the only way to change the order at this point is to add the categories in the desired order. This is also the first time that I have added extra data to the database model that will only be used by the mobile app. The main app should ignore the additional properties, so we'll see how things work.
Also, if you haven't noticed, the easy tasks are being knocked off the list first. The next feature to be added will likely be the budget amount editor, and that's going to take some effort...
Edit: You'll likely have to unpin all categories and then pin the desired order for it to work correctly. There are a few issues with the sort indexes that will be ironed out at some point.
v0.4.16 released: Final release of the day. Fixed category "Add Transaction" and "Pin Category" menu spacing. Fixed frequently used transactions not disappearing when typing in the search box in the payee editor.
Edit: One more thing... tweaked menu icons and made them a little colorful.
My wife asked, “What if I want different categories pinned on my phone than what you have on yours?â€
I should make syncing optional for that.
Quote from: asromzek on December 16, 2017, 09:31:11 PM
v0.4.16 released: Final release of the day.
Crikey I don't check the forum for a day or two and there are three new features added. :parrot: looking good, really good!!!
Locally pinning categories is going to be a little more difficult than expected. I took a crack at protyping some stuff last night, and ran into some headaches. I may have to table that until some other features, like budget value editing, are out of the way.
I pushed out a small change to prepend pinned category names with a color themed pin icon in the pinned list, and a light grey icon in the normal list. This should make the pinned categories pop out a little bit. Just a minor change, so no version update.
v0.4.17 released: Budget editor (calculator!) has been implemented. I have had a very, very long couple of days and I'm half asleep, so there may be a few rough edges. Check it out and let me know what you think...
Edit: Quick budget options are soon to follow.
Of course, right after I release the budget calculator, I find that you can divide by zero with the calculator. I recommend not doing that until I can fix it. “Infinity†screws things up... :o
v0.4.18 released: Added better NaN and Infinity checks, and increased button font size for budget value calculator. Fixed parenthesis appending to a zero value when they should overwrite it.
Woke up early, and had to fix these nagging issues before work. Coffee time.
v0.4.19 released: Swiping left and right in the budget view moves the selected month forward/backward, at least in Safari. I wanted to animate it to make it a little more obvious, but it's not very easy with the current layout. I may enhance this later.
Can those with Android let me know if it works?
Indeed, Nexus 5X 8.1.0 swiping is working, to be honest it does seem a little insensitive in that you have to swipe perfectly horizontally, more so than other apps but once you get the hang of it it's all good.
There are settings to adjust the sensitivity, and I'll look into that tonight. I think it may fight with the category list trying to scroll up and down, but I'm not sure if that can be remedied.
No worries, sounds good!
What do you guys think about having the Available to Budget and Totals compress a little more when collapsed?
Personally I prefer it compressed more.
v0.4.20 released: Quick budget options for individual categories, and for all categories in the selected month have been implemented. The budget header was also compressed to eliminate some wasted space.
Only a few more things to wrap up (notes, notes, notes), and I think we're going to have v1.0.0 in our hands...
v0.4.21 released: Category and budget cell notes have been implemented. There is still a little formatting to be done, but the basic functionality is there. Fixed budget calculator not formatting currency decimal point correctly. Added main quick budget header and adjusted menu text in few places.
Account notes are coming. Also, be aware that if you have a category pinned, and edit the note for that category in the main app, it will be unpinned because the main app stomps on my special properties. Not a big deal because synced pinned category settings are likely going to go away, being replaced by local settings per device.
v0.4.22 released: Account notes implemented.
It's fun looking back at some of the early code I wrote while learning Vue.js. I'll go back and clean up some of the messes I made later...
Before going any further, I will be adding the ability to create/edit/delete/sort budgets, accounts, master categories, categories, etc., so you can use/test the mobile app completely without requiring a paid account. Reconciling accounts is also something that I want to add. This may help some people with their decision to pay for the syncing option, if they can see how both apps work in their entirety.
v0.4.23 released: Master categories are now collapsible. (Master) category drag & drop reordering has been implemented. Categories can sorted and moved between master categories. Master categories can also be rearranged, and it's a lot easier if you collapse them before doing so. Reordering does not take effect until you press and hold on a category or master category for more than half a second to make sure scrolling and swiping still have a chance to work.
These new features are to be considered experimental. Please report any weird behavior. Account reordering will follow soon as long as the category reordering looks stable enough.
v0.4.24 released: Pinned categories no longer sync across devices, and will be treated like a local setting. Sorting pinned categories via drag & drop is now enabled.
Why am I still awake? :P
Looks like the SSL certificate has expired :( new features sound good but cannot get in.
Quote from: ottyacat on December 25, 2017, 06:37:50 PM
Looks like the SSL certificate has expired :( new features sound good but cannot get in.
Looks like I screwed something up while moving the mobile app to new web domain...
Introducing: https://app.fmobile.io (https://app.fmobile.io)! :parrot:
Yep that will do it, a nice shiny new home. :)
I'll fix the SSL stuff on the old site and put up a message that the app has moved. The move was supposed to be a surprise, and I screwed it up!
Oh no.. Well still cool thanks for all your efforts. PS I'm not sure how to test reorderibg the categories. I have tried just dragging, click and hold but not sure what's i am missing.
If you tap and hold for a least a half second, you should be able drag & drop to reorder or move categories. If I remember correctly, you're using Android? If so, what browser?
Edit: Also, if you tap the menu button in the top left and then go to the About menu, what version of the app does it say is running?
0.4.24
Ok yea that's what I have been trying, I actually got it to work once but now it's not working at all.
You remembered correctly, android, chrome browser.
I have noticed some odd behavior while testing with Chrome on Windows while running the website in "mobile mode". If you refresh the mobile app, does it work once and then stop working until refreshing again?
No not really, well it did once and then subsequent refreshes are still not working. Its quite random like one in 20 or 30 attempts will work.
It looks like the drag & drop functionality is disabled once you scroll the category list, at least in Chrome. If I refresh the page and very carefully click and hold on a category without scrolling first, reordering is possible, and repeatable. As soon as I scroll the list, drag & drop no longer works. This will be a "fun" one to sort out, if possible.
Ahh yea i see what you mean, I chucked it into dev mode on my desktop and it behaviours exactly like you say in chrome. I have tried it on my mobile countless times but maybe my fingers are just not accurate enough to trigger it without a scroll. It indeed sounds like it will be a challenge :-\
Alight
@ottyacat, give v0.4.25 a shot and let me know if it's cooperating now.
Quote from: asromzek on December 25, 2017, 09:56:46 PM
Alight @ottyacat, give v0.4.25 a shot and let me know if it's cooperating now.
Ok so no difference on my Nexus 5X ive tried in the browser directly and via a homescreen icon, same thing. But it's working fine on my Samsung tablet, very strange!
Is it possible get the version of Chrome you're running on your Nexus 5X, and this is probably a dumb question, but did you make sure to refresh the app and verify that v0.4.25 is loaded? I know some older version of Chrome had some bugs with touch gestures and stuff like that.
By the way, I'm downloading an Android emulator now...
It's the latest one available from the play store (63) I think.
I did do a refresh and make sure the version said 0.4.25 u fortunately :( there is a beta version of Chrome. I will give that a shot
After doing a lot of research tonight, it looks like Android has a number of issues with drag & drop in a variety of situations. I'm going to have to table this until I can get a good emulator up and running, and/or get my hands on an Android phone once and for all. The joys of web development! ;)
Indeed and I guess that confirms at least I'm not going mad :P
@ottyacat, would you be able to test with Firefox on your phone to see if it’s an issue specific to Chrome?
Sure thing, I installed the latest Firefox and it is sort of working but probably not properly. So when you click and hold the row for a second it then let's you move the row but then as you start moving the row it also starts scrolling and thus you cannot really move it anywhere because it's scrolling the whole screen at the same time as trying to move the row. The work around is to click and hold the row and then use a second finger to stop the screen scrolling, then you can move the row.
At what point is it appropriate to suggest getting an iPhone? :D
Maybe the attachment will answer that question. 8)
To be honest, I just like QA testing stuff, moving categories around doesn't really affect me one way or another ;)
Wednesday (Thursday?) Update: I did nothing today, literally. Pants didn’t happen. Two pots of coffee. Microwaved every meal that needed to be warm. Binge watched Future Man on Hulu. You know, standard vacation day schedule. It’s amazing how the best development occurs when free time is scarce or non-existent.
Seriously, watch Future Man if you like stupid sci-fi and don’t have kids in the room. (Produced by Seth Rogan)
Quote from: asromzek on December 27, 2017, 11:35:54 PM
Seriously, watch Future Man if you like stupid sci-fi and don’t have kids in the room. (Produced by Seth Rogan)
Sounds good! Don't think we can get hulu in Aus, we'll legally anyway. I'll have to investigate other methods. ;D
How hard would it be to persist the collapse status of the budget master categories, even just in local storage? I find my myself satisfying my OCD every time I visit the budget screens and collapsing my hidden master categories over and over again. :P
Actually, master category collapsed memory is a syncable property in the main app. I considered having the the mobile app tie into that, but it might be preferable to have that as a local setting. That way you can quickly scroll on mobile, expanding only what you need to see, and still see everything on the main app when loading it up.
I’m also trying to figure out how to squeeze in a collapse/expand all button.
Sounds good! I reckon next to the Categories label would work just a simple word collapse that changes into expand. Etc
PS the whole swipe left and right is working much better now, not too sensitive any more, definitely feels like it's been tweaked. Either that or my phone was having another moment. But it's good now!
Quote from: ottyacat on December 28, 2017, 02:06:25 PM
PS the whole swipe left and right is working much better now, not too sensitive any more, definitely feels like it's been tweaked. Either that or my phone was having another moment. But it's good now!
I made some adjustments to that last week. Cranked the sensitivity from 30 to 100... I'm not sure what units that is, but it seemed more responsive. :P
I also thought of a new quick budget option that I would find really useful toward the end of the month. "Cover overspending" for categories that have a positive balance. If your available to budget value is currently negative, choosing this option would try to unbudget money from a category to cover the current overbudgeted amount. Only the amount needed would be unbudgeted if possible. The category would simply be budgeted to zero if the balance does not exceed the overbudgeted amount.
Quote from: asromzek on December 28, 2017, 03:12:09 PM
I made some adjustments to that last week. Cranked the sensitivity from 30 to 100...
Lol love it! When in doubt, crank it to 100 ;D
Quote from: asromzek on December 28, 2017, 03:12:09 PM
I also thought of a new quick budget option that I would find really useful toward the end of the month. "Cover overspending" for categories that have a positive balance. If your available to budget value is currently negative, choosing this option would try to unbudget money from a category to cover the current over budgeted amount. Only the amount needed would be unbudgeted if possible. The category would simply be budgeted to zero if the balance does not exceed the over budgeted amount.
An interesting idea, I would probably use something like this. Although I have several long term categories that i never like to touch and in these instances would not want money taken from them . How would you select which category to cover it from? Largest balance would probably hit these longer term accounts.
This would only work with one category at a time, and it would be added to the list of quick budget options. If the current global available to budget is -$5.00, and you currently have a balance of $30.00 in Groceries, the "Cover overspending" quick budget option would subtract $5.00 from the current budgeted amount for Groceries, taking the balance to $25.00, and available to budget to $0.00. If you only have a balance of $1.00 in Groceries, then that full amount is unbudgeted taking the balance to $0.00 and available to budget to -$4.00.
Does that make sense?
Quote from: asromzek on December 28, 2017, 04:25:52 PM
Does that make sense?
Ahh yea i misunderstood, that sounds really good!
To better explain how I would use this...
At the end of the month I like to go through my budget and use the "Budget to Zero" on all negative categories. This sometimes results in a significant negative Available to Budget value. Then I could run through all of my positive categories and suck money from them one by one until Available to Budget is $0.00 again. Starting with the less critical categories.
Yea that sounds like a pretty good process!
I think I'm just going to use the mobile app on a full browser instead of app.financier.io.
I'm also looking for a few quick budget options by category:
Average expenditure last 3 months
This year
Last 12 months
Expanding the quick budget stuff is on my list, especially the average expenditures over the last X months.
v0.4.26 released: First release of the year! Although, it's just a small one. Tapping on a positive category balance when the available to budget value is negative will display the option to "Cover Overspending". The amount of money needed to cover the overspent amount, or as much as the category can provide, is unbudgeted from the category and move back to the available to budget amount.
Hi
@asromzek, I noticed that if money is unbudgeted in a month (green) it displays in the budget header of the following month as "Overbudgeted in xxx".
Good catch, that label should change to "Not Budgeted in XXX" when the previous month's available to budget zero or positive, and "Overbudgeted in XXX" when negative. It's on the list of bugs to fix.
Hey
@asromzek, love everything you’re doing with the mobile app.
Wondering how hard it is to implement settings to custom adjust the font size. I’m sure it is a formatting nightmare, but I would like the option if it’s possible.
Thanks!
@michaelmjd, changing font size dynamically may be a little tricky since it's hard coded throughout the app, and most of the text is sized to fit the layout. Do you find the fonts are too small or too large?
Also, what kind of device, OS, and browser are you using?
v0.4.27 released: Just a few minor updates. Added "Note" placeholder and clear icon in all note input textboxes. The selected month in the budget is remembered when leaving and returning to the budget view during the session. Fixed label text in budget header to display "Not budgeted in XXX" when the previous month's available to budget is zero or positive, and "Overbudgeted in XXX" when the value is negative.
These were a few nagging issues that I wanted to resolve before adding some heavier features.
Font size is a little small for me, but not unusable. I’m just thankful to have the mobile app to use.
iPhone 7; iOS 11.2.1; safari
Agreed.
I noticed that the font scaling on chrome has no affect.
Pixel XL, Android 8.1, Chrome
I sized the app to fit on an iPhone 4 screen, which doesn't provide a lot of real estate for the amount of data to display. It doesn't make sense to keep the text tiny on large devices, though. The entire front end needs an overhaul under the hood anyway, so I'll add text sizing to the list. I will likely make all of the text throughout the app the same size, and add a drop down or scale to set the desired text size. This may also require some layout scaling to contain the text cleanly in certain areas.
Quote from: asromzek on January 06, 2018, 11:24:57 AM
I sized the app to fit on an iPhone 4 screen, which doesn't provide a lot of real estate for the amount of data to display. It doesn't make sense to keep the text tiny on large devices, though. The entire front end needs an overhaul under the hood anyway, so I'll add text sizing to the list. I will likely make all of the text throughout the app the same size, and add a drop down or scale to set the desired text size. This may also require some layout scaling to contain the text cleanly in certain areas.
Who uses an iPhone 4 thesedays? It's 2018!
I should have said iPhone 5, since they have the same screen width. ;)
Last night I made an executive decision to break the app into a couple pieces, specifically to separate the core budget auth/data engine into its own library. I should have done that from day 1, but the mobile app was not intended to be as complex as it is now. This will make the data engine available for other apps to use since all front end dependencies will be completely stripped out. And data bug fixes can propagate to all apps that use the library.
This will not be a simple task, but I think it’s necessary at this point, and it should improve the ability to build additional tools.
Monday (technically Tuesday) Update: I put about 7 hours into building the new core library tonight, and I'm roughly 1/4 o 1/3 of the way through it. This is the easy part: copying files over, reorganizing things, and revamping a few hundred comments. The difficult task is coming: ripping the old data code out of the mobile app, and wrapping it around the new library. It's particularly difficult because I'm fundamentally changing how the auth and budget data is handled, so the mobile app will need some significant refactoring in a few places. Things are not going to line up perfectly. In the end there will be a much cleaner separation between the internal data model and the front end, making it easy to use the data model in other apps.
To be continued...
Thursday update: Not much to report. I've been at every night this week. After heading down a few wrong paths and backtracking a couple of times the code is starting to come together, piece by piece. I'm going to keep my head down and continue pushing forward...
FYI, a small amount of mobile app downtime will be occurring this afternoon as the Digital Ocean server that hosts the app is "upgraded". Same specs, half the price. :parrot:
Edit: Complete.
Wednesday Update: Finally back in the saddle this week. Made a modest amount of progress last night, mostly consisting of figuring out where I left off, and then tracking down a really annoying, self-induced authentication bug. The good news is that I have most of the code moved over to the separate library, and the mobile app is working with the imported code. However, there are quite a few structural changes that are needed to make the library more autonomous, and that means ripping some more code out of the mobile app and then updating a couple hundred references throughout. It's something that needs to be done in one major series of changes, and I want to make sure I reserve enough free time to do it in single sitting...
Huh, anyone else having issues entering transactions in an off budget account with the mobile app? :o
hmm not that i am aware of, just tried one now and it seemed ok
The "Save" button on the transaction editor is definitely not responding for me. What version is listed when you go to the About menu?
0.4.17
Ahh yea I am suffering the same problem! It appears to be related to the payee field, if I leave it blank it works as it did when I tried yesterday. But if I do enter a payee (as I normally would) I cannot save.
Looks like a bug was introduced when I added the ability to create transactions from the budget view. I'll fix that up this weekend. Are you sure you don't have v0.4.27 (current)?
Yea sorry your right, must have been a slip of the finger on the mob ;)
v0.4.28 released: Fixed the bug that inhibited transactions from being entered in off budget accounts. Also fixed some missing "Category Not Needed" messages. Semicolons are now enforced throughout the source code, which doesn't really affect anything on the front end.
Edit: I missed one small change that I wanted to make, which is renaming the quick budget option "Cover Overspent" to "Cover Overbudget". I pushed that additional change without bumping the version.
Friday (I think?) Update: Crushed by work, family, and hobbies over the last few weeks. I am planning to do as little as possible this weekend (real life hard reboot).
Sometimes I think it is healthy to walk away for a while.......... You do deserve the rest :) :) :) :)
Monday Tuesday Update: If only I could provide a real update... Life has sucked up all of my free time lately, and the small amount of tinkering that I've been able to squeeze in hasn't amounted to much. I actually had to start using a real calendar to schedule my time efficiently, and there hasn't been any available time slots for side project development. The next week isn't looking any better, but I'm going to do my best to get the train back on the tracks. Getting it moving will be another story...
No worries! It happens to the best of us! I'm just happy there is someone who has intent to make sure this program doesn't completely stagnate. Any progress is better than no progress!
It's going to take some effort to get back on track with developing the mobile app. Is anyone aware of any bugs or annoyances with the mobile app that would act as some low hanging fruit? If not, I'll see if I can figure out where I left off..