izettle / wrench Goto Github PK

From action bar? or from application list?

And any other configuration set in their androidManifest that could leak / set weird configuration on including applications.

if you editing a field and press restart icon the setting have not been changed because of the focus have not yet left the editText

When using the "restart application" button in the toolbar we should make sure that the last edited configurations will be applied before we do the restart of the application. Right now it's being saved onFocusLost() or something similar. This solution is not smart enough.

As the list of configurations is rapidly growing we should implement a way to highlight which configurations are in use ("my") and which are the remaining.

One idea would be to put the used ones in the top with a highlighted background.
Another would be to have the user explicitly "favorite" a configuration that she/he want's to use and then be able to filter on the "favourited" configurations.

This behavior should survive restart (of the local-configurations app)

To be able to perform a programmatic delete of keys you want to use their fallback

After checking it out I get these errors,
which should probably be inserted in the readme on how to take care of building.

I can probably navigate through it, but not everyone knows how.

String backed properties could be cumbersome to type over and over when you want to to tests your app with and without the configuration property set.

It would be great if you could have a Disable button that disables the property, but keeps the entered value, in conjunction with the current Revert button which disables the property and clears it's value.

Some kind of sorting / surfacing "my" used configuration.
Separate default values from modified values?
How many times it has been toggled?