[Android Software Development] Brut.all:
FEATURES DESCRIPTION AND NOTES

1.5. Change colors of factions.

I did this before and it's kind of cool: https://plus.google.com/u/0/106080343103638200670/posts/a9krpWApjz5 :)

2.4. New portal keys screen.

I have some ideas, e.g.:

keys grouping/tagging

group/tag keys manually or automatically by their location, name, etc.

filters and sorting by: name, distance, level, owner, etc.

, but I think Niantic want to improve keys management, so I wait for their move.

2.5. Remove original items screen.

For now even if you prefer new items screen the original one is still needed to access portal keys. We can wait for 2.4. or at least add an option to limit original items screen to portal keys and rename it accordingly.

2.6. Shortcuts to various actions from the main screen.

I think it's one of the most important additions, so it has to be well designed. I see it as a HUD-like buttons similar to "FIRE XMP" when you long-press on a map, but much smaller, probably square with icons. Things to consider:

toolbar at the top or the bottom of the screen - I think it's better than left/right

fixed with 5-6 icons (4" screen) or scrolling horizontally

fixed icons or customize them and their positions

an option to open a full semi-transparent menu with all available actions

Actions could be:

fire last XMP

fire highest/lowest XMP

fire XMP of specific level

same for power cubes

hack portal - click button then click portal. This way you don't have to enter portal details screen which is faster and you don't lose the map.

link portal - same as above

set target? It's in a long-press menu already, but we can add it here for consistency and maybe to remove long-press menu.

actions from other mod additions

2.7. Modify chat to make it easier to read and harder to accidentally send private message to the public channel.

Current problems are:

is there anyone who has never sent a private message to the public channel? Is there anyone who did this only once or twice?

it's hard to read conversations between agents, especially public ones, because they're mixed up with system messages

I was considering adding some kind of filters to select which types of messages you want to see, but it doesn't fix first problem. Now I think of something else - 4 tabs/channels:

faction - as normal

public - public conversation only, so system messages won't disturb you and you don't accidentally respond [secure] messages

system - you can't send a message here

all - all above, so it's similar to current "All", but you can't send a message here - you have to choose proper channel intentionally. It can have additional filters to select messages to show.

This feature may be hard to do or even impossible, because most probably Ingress server doesn't have API to filter messages as above. Of course I can read "All" channel and filter it on the app side, but it may not be that good.

Also I won't be surprised if Niantic itself will redesign chat in the near future, because it's definitely wrong.

2.10. Additional info about the portals directly on the map screen.

E.g.: level, if you have a key (how many?), etc. It could be customizable and there could be a shortcut to toggle showing this info.

2.11. Logging and statistics.

I love this one :) I can log all kind of actions like: hacking, attacking, dropping and picking up items and XM, deploying resonators and portal mods, adding custom "snapshot points" to organize above, etc. and then create a lot of various statistics:

how many hacks did you do (faction, enemy, neutral) today, in last week or month?

how many items did you get from these hacks?

what were the levels of hacked portals and items?

how many XM did you get?

how did you spend this XM?

how many resonators did you deploy and what were their levels?

how many resonators did you destroy, how many portals did you capture?

how many links and CFs did you create/destroy, what were their MU values?

which portals do you hack/attack/build most often?

how much time you was playing?

what items did you spend to build up a farm and what items did you get from it?

Statistics could be tabular, graph, pie and very flexible. I'm also considering two things:

sending some of above statistics to my server to create global statistics for all users. It would let us do some research, e.g.: what is the probability to get L7 item from L6 portal, etc. Of course sending these statistics would be fully optional, you would have to enable it by yourself.

optional paid application to read these statistics - in addition to the free one. It could let you remove ads or just say "thank you" (i.e. it would be the same as free one), but I don't want to piss off someone in Niantic. I think it would be fair, because statistics app would be quite complicated and time consuming and there will be free version, but you never know what's the opinion of other people.

What do you guys think about above two things?

3.5. Auto deploy resonators using a template.

Agent can configure multiple templates and choose one of them when doing an auto-deploy. Template could be defined by:

its name

minimum and maximum level for each resonator

prefer lower/higher level for each resonator

Examples:

"Lowest portal" - each resonator set to L1-L8 and prefer lower for all - it's the same as clicking "deploy" 8 times.

"Highest portal" - L1-L8 and prefer higher for all

"Highest <L7" - L1-L6, prefer higher for all

"Standard L4" - L1-L6, L1-L4, L1-L5, L1-L4, L1-L6, L1-L4, L1-L5, L1-L4, prefer higher for all - it's standard 4xL4 2xL5 2xL6 and it'll use lower resonators if you don't have all of them

another "Standard L4" - same as above, but L6-L6, L5-L5 and L4-L4 - it won't automatically downgrade resonators, but warn you about the lack of resonators

Also some templates could be predefined by default.

It won't work well with existing resonators, it won't choose optimal way to upgrade them, but this is how it should be - it's just: "do it using a template", not: "Calculate optimal situation".

3.6. Templates specific to a portal.

Extension to above: sometimes you know that e.g. NE resonator of some portal is harder to destroy, so you want to place highest resonator there. You can create a template specific to a portal, so it won't mess up main list of templates and it will be auto selected when doing auto deploy for this portal.

3.7. Other agents presence detector.

It read system messages log to find the last actions and positions of other agents (actually positions of portals they've built/attacked). This information could be used to e.g.:

show last position and action of specific agent

show a list of nearby agents: allied or enemy

alert if some other agent will show up below specific distance from you

4.3. Smart auto-deploy.

E.g.:

calculate max level of a portal that you can build alone - depending on your inventory and already deployed resonators

deploy minimum number and optimum resonators to get to specific portal level

prioritize excess resonators and save scarce ones

deploy high and low resonators evenly to make attacking a little harder

if upgrading existent resonators, prefer to upgrade ones with low XM

4.4. XMP damage assistant.

E.g.:

approximate damage dealt using specific XMP in current position

calculate the best spot to fire XMP of some level

4.5. Linking assistant for optimum CFs in a specific area.

You select a group of nearby portals, assistant build links and guide you through place to get as many CFs and AP as possible.

4.6. Continuous linking assistant.

You see an icon near the portal if it's possible to create a link(s) from it to create a CF. It let you create this CF with few clicks.

It may be not possible to do, because it would have to scan big area to know if there are a link between remote portals.