Nicholas Killewald

Well, here's what I've got. Sorry it's taken me a while, I've been a bit busy with other stuff. Version 0.9.6.6's only functional change is the signing key (and it's...

Yeah, that sounds like a decent plan. Though if something comes up that necessitates a functional update before then, I'll likely just sign that with the new key.

Currently, you would put the API key in a string resource named "api_map_key_v2" You'd have to make your own resource file to put it in; I just have a local...

Regarding private.xml, you'd add that as a resource file in `/app/src/main/res/values`. Android checks there for top-level resource files without any qualifiers (you may also see a `values-night` directory; that's the...

Regarding the key rotation, I'm afraid I don't have much answer beyond what I've already done. What I did was as far as I could read from the Android developer...

Regarding key rotation, if that's the case, the uninstall/reinstall solution is going to be the only option. Regarding the rebuildability, it sounds like you're building from the repo tag of...

Yes, you should switch to the new key now. There should be no issue with future releases concerning the date string, as I update that manually when I make a...

Thank you for the PR, but I'm afraid I'm not interested in merging that into the codebase. Sorry.

Thank you for the PR, but I'm afraid I'm not interested in adding this to the project right now. Sorry.

Honestly, what about a customizable main toolbar? I'm starting to think maybe that might be a better bet here. I went with the toolbar it has now in an effort...