adammc331 / cashcaretaker Goto Github PK

After an item is long clicked, add some tint to the item to show which one was selected.

Allow user to add transactions that repeat at a set interval (monthly, yearly, etc).

This would be a really nice way to provide quick actions to items for an account.

https://developer.android.com/guide/topics/ui/shortcuts.html

When the user first loads the app, there are no accounts or transactions to view. The screen is blank and it may not be obvious what to do, so add a hint.

Will want something to run tests on each PR.

After watching the Udacity course on Wear development, I realized I'm using poor development decisions on Wear.

We should use Data Items instead of Messages, since they are always guaranteed to be delivered when the Watch/Phone sync up. In addition, we should reduce the amount of operations the watch is doing to save battery. We should consider having the watch request information from the phone when the watch activity starts, and the phone will spit back a response and the watch can cache it as necessary.

Planning to do a release focused on this: 1.4.2

Create a view that allows the user to enter a new account. We will need to collect:

• Account Name
• Starting Balance

While having a ContentProvider is nice and works for the super simple CRUD things, I'm tired of writing new URIs every time I need them when it's a bit unnecessary, since this app doesn't display any data externally.

The CCProvider class will be replaced by CCDataSource which will run all of our operations.

NOTE: With overhauls like this, the milestone might turn into 2.0.

Allow the user to view a list of transactions for a specified account.

Pretty self explanatory. See blog post for reminder on FloatingActionButton.Behavior: http://androidessence.com/hide-the-floatingactionbutton-when-scrolling-a-recyclerview/

Need to rewrite some of the content provider code from the original app module.

Add a header to the RecyclerView.

Before releasing update 1.4.0, run code analysis and clear up a lot of clutter.

Did not disable swipe to dismiss on the activity as specified in the docs: http://developer.android.com/intl/pt-br/training/wearables/ui/exit.html

Need to correct this.

Test all required implementations of the content provider and each URI it supports.

Add the Timber logging framework by Jake Wharton - https://github.com/JakeWharton/timber

As beautiful as this library is, it adds a lot of methods to the method count of the app and when updating some gradle dependencies the app went over single dex. Changes have been reverted for now, but JD will likely need to go in the future to keep down app size.

Currently a user can enter a transaction for any date and it will affect the account balance, including if the transaction is set in the future. Find a way to set this up so that transactions don't change account balance until it is time.

Add date to transactions and sort by date descending on the transaction view.

Gradle is outdated on CC.

Need to disable backup in the AndroidManifest.xml

Add an icon to differentiate recurring transactions from normal ones

Show a fragment that has key information about the app like icon, version name, 3rd party libs, etc.

Find a way to extract 'AccountDialog', 'CategoryDialog' and 'RepeatingPeriodDialog' to the same bit of code since they are all similar.

It has to happen.

Support a master-detail flow for tablet layouts.

Just need to remove the wear module completely until it can be rewritten correctly.

Would make life easier for both data storage and login. Could use Google auth.

Now that we have a login activity, we should have a nav drawer home screen that shows the user's info

Add a small hint below account balance of the next incoming recurring transaction
ex:

account balance: 1923.22€
pending recc. total: - 281€

Allow the user to enter a new transaction. Will need to collect:

• Description
• Amount
• Notes
• Date
• Category
• Withdrawal or deposit

Update the fragment to accept input for editing an existing transaction.

Currently the categories is a hard coded list. Allow the user to manipulate and manage their own categories.

After conversations on #22 I would like to implement the Fabric SDK as well.

Allow the user to add/remove categories for their transactions.

This can be used to parse receipts and do your best guess at recording the information automatically.

Allow Users To Transfer Money From One Account To Another

As part of my attempt to do a kotlin refresh (all/mostly non-UI updates), I'll be creating new tickets for all of the tasks that need to be done. This is the first of those tickets, they will all be part of the "Kotlin Refresh" milestone.

Need to create a landing page that shows a list of the users accounts.