Intel suggestions for +NIA Ops
As someone routinely laughed at for never using IITC (since it is a supposedly ban-worthy offense) I have always relied on stock Intel for everything from planning a day of hacking to planning ops (I cheered when the link tools were put in). I can no longer do these things due to the changes to Intel - which is now even slower than it was before portals were taken away.
But, I want to make some positive suggestions... So here goes... apologies if these have been suggested before.
1. Provide an option to disable the COMM. This would remove load times on the COMM within the map view.
2. Make showing portals, links or links of a certain length into optional layers you can turn on or off. This would include the option to only show portals and NOT links (useful for building links using the link tools).
3. Get this out of the browser and make an app for Intel. It doesn't need to be in the Ingress scanner but that would be cool too. Alternatively, just bless IITC so rule-abiding ppl like me have a real option.
4. When you draw a link using the draw tools, make it so that mousing over that link will show the number of blocking links. This helps you know if you need to zoom in and follow the entire lane to find a tiny unshown link or not.
5. Provide a version (or option) of the intel map with the portals but without live status info. I.e. - allowing you to build your dream fields without the constant refreshing. Then you could turn on the "live" view to see what is in the way. This should significantly reduce load times to scroll around the map and build your links.
6. Since you are logged into Intel and it knows you, have an option to highlight (as a layer or separate symbol/color/whatever) portals for which you have a key in your inventory.
For me, one of Intel's biggest problems is that it is trying to be too many things for too many people instead of allowing the user to determine how they want to use it. If my goal is to find portals or portal clusters in my city, that is very different from wanting to plan a fielding op over my state or from wanting to scan for enemy fields to take down. Allowing the users to determine the content they want to see, vs. pre-determining that based on "zoom level" would be a better UX and would also reduce load times and server load for many use cases.