@Perringaiden my point being, this "feature", whatever it was intended to be, is not useful as it stands. See also @InvestigateXM 's thrilling debugging several comments back (August 5th).
Please don't try to defend broken behavior by saying "well, that's how they made it." or claiming "what you want is out of scope".
MY ENTIRE POINT is that how they made it is not useful. It's broken. I would rather not have whatever this is than have it as it is now. If you agree it needs improvement, don't c-rap on other people's criticisms of it.
[IBM: acronym, “Broken As Designed”] Said of a program that is bogus because of bad design and misfeatures rather than because of bugginess. See working as designed.
working as designed: adj.
[IBM]
1. In conformance to a wrong or inappropriate specification; useful, but misdesigned.
2. Frequently used as a sardonic comment on a program's utility.
3. Unfortunately also used as a bogus reason for not accepting a criticism or suggestion. At IBM, this sense is used in official documents! See BAD.
MY ENTIRE POINT is that how they made it is not useful. It's broken. I would rather not have whatever this is than have it as it is now. If you agree it needs improvement, don't c-rap on other people's criticisms of it.
Right, but that's where we disagree. For what Niantic intended to implement, it satisfies all needs. It does exactly what it was intended to do.
You're adding requirements that otherwise don't exist and were never intended, then claiming it's broken because it doesn't meet your expanded requirements.
You can say you want more. You can't claim it's broken according to it's own requirements. It was never intended to be an always accessible profile. It's literally just a deep link to a profile in the app.
Seeing as how neither you nor i work for Niantic on the Ingress Dev team, neither you nor i really KNOW what the "exact requirements" were.
my claim is merely "as delivered, it appears broken, or is useless at best".
i NEVER claimed "it doesn't meet the mysterious internal to Niantic only specification that i've never actually seen". YOU are the only one to have made claims about this "specification".
I still would like to see you address the problem @InvestigateXM discovered, as well as the fact that you actually CAN open an app from chrome in android (see my previous comments).
also, if your claim is "niantic delivered exactly what they intended", that does not invalidate my claim that "what they delivered is a piece of junk that can be made better".
you seem very choosey about when you do and don't want to defend Niantic's implementations of things.
I agree that they should implement a Web Profile. That's why I posted the thing I did some years ago. However, this was not a feature to provide an always accessible profile. This was providing deep linking for Portals, which they easily extended to open the existing Profile. That's what they said they were providing, provided, and did not 'break'.
Minor enhancement to another feature (portal deep linking) vs writing an entirely separate feature. And I know from personal discussions with some of the Devs when I used to live in LA, that HTML/Javascript knowledge (at least at the time) was slim in the team, so anything they could do through engines and the client was a far better option.
I want a web profile. But that's a separate feature unrelated to deep linking access to Client screens. This is how software development works.
This was a "Deep linking to screens" feature. It was not a "Make the profile available everywhere to everyone" feature. If you've got 30 years experience, you should know better and quit scope creeping like a bad client.
ALL clients scope cre ep. If you had any experience, you'd know that. it's why i charge by the hour.
Also, please stop claiming you have internal knowledge about what the original feature entailed, and what is and is not in scope. you have no idea. you don't work for Niantic.
Don't want to enter the discussion, but a small clarification: The problem is that Chrome doesn't open an app when opening a link via the address bar. Chrome does open a link via an app when you tap on it while it's embedded in a Website, which is what Reddit does.
What Niantic could do is design a simple landing page for now that, instead of redirecting you to Ingress.com (assuming the link wouldn't be broken), it would show something like "This link can only be opened with Ingress Prime. >Open in App|>Download Ingress Prime". If you'd then tap on "Open in app", Chrome sees it as "The user specifically opened the link, lemme see if there is an App that can be opened" and would open Ingress.
Chrome does open a link via an app when you tap on it while it's embedded in a Website, which is what Reddit does.
So does Ingress. That's already described above. If you paste the link into Telegram for example, then click on it, it opens. That's not what the whining was about though.
If you want a web profile, sign on to the post I made or make your own. New feature, new post, new discussion. Attacking the developers for "failing" or making "broken features" has zero effect except to tell them to ignore you.
So if I have to spend my time teaching you what you should have already learned from 30 years in software development, it's a productive use of my time (assuming you learn).
<<If you want a web profile, sign on to the post I made or make your own.>>
what are you talking about? Web profile? "sign on to the post you made"? srsly, what are you talking about? no srsly, what are you talking about?
re: you teaching me a lesson. 🤣🤣🤣
another thing i've learned after 30 years. harping on the exact language someone uses when pointing out deficiencies in a product is an utter waste of time. grow some skin already. a good software engineer will look past that, see what problems the client has, and work the problem. attacking your client just loses you clients. (in case you missed it, we the players are the client in this case).
and clients attacking other clients for pointing out deficiencies? well that's just Stockholm Syndrome.
Comments
@Perringaiden my point being, this "feature", whatever it was intended to be, is not useful as it stands. See also @InvestigateXM 's thrilling debugging several comments back (August 5th).
Please don't try to defend broken behavior by saying "well, that's how they made it." or claiming "what you want is out of scope".
MY ENTIRE POINT is that how they made it is not useful. It's broken. I would rather not have whatever this is than have it as it is now. If you agree it needs improvement, don't c-rap on other people's criticisms of it.
@Perringaiden from the MIT Jargon File:
BAD: /B�A�D/, adj.
[IBM: acronym, “Broken As Designed”] Said of a program that is bogus because of bad design and misfeatures rather than because of bugginess. See working as designed.
working as designed: adj.
[IBM]
1. In conformance to a wrong or inappropriate specification; useful, but misdesigned.
2. Frequently used as a sardonic comment on a program's utility.
3. Unfortunately also used as a bogus reason for not accepting a criticism or suggestion. At IBM, this sense is used in official documents! See BAD.
MY ENTIRE POINT is that how they made it is not useful. It's broken. I would rather not have whatever this is than have it as it is now. If you agree it needs improvement, don't c-rap on other people's criticisms of it.
Right, but that's where we disagree. For what Niantic intended to implement, it satisfies all needs. It does exactly what it was intended to do.
You're adding requirements that otherwise don't exist and were never intended, then claiming it's broken because it doesn't meet your expanded requirements.
You can say you want more. You can't claim it's broken according to it's own requirements. It was never intended to be an always accessible profile. It's literally just a deep link to a profile in the app.
Seeing as how neither you nor i work for Niantic on the Ingress Dev team, neither you nor i really KNOW what the "exact requirements" were.
my claim is merely "as delivered, it appears broken, or is useless at best".
i NEVER claimed "it doesn't meet the mysterious internal to Niantic only specification that i've never actually seen". YOU are the only one to have made claims about this "specification".
I still would like to see you address the problem @InvestigateXM discovered, as well as the fact that you actually CAN open an app from chrome in android (see my previous comments).
also, if your claim is "niantic delivered exactly what they intended", that does not invalidate my claim that "what they delivered is a piece of junk that can be made better".
you seem very choosey about when you do and don't want to defend Niantic's implementations of things.
I agree that they should implement a Web Profile. That's why I posted the thing I did some years ago. However, this was not a feature to provide an always accessible profile. This was providing deep linking for Portals, which they easily extended to open the existing Profile. That's what they said they were providing, provided, and did not 'break'.
Minor enhancement to another feature (portal deep linking) vs writing an entirely separate feature. And I know from personal discussions with some of the Devs when I used to live in LA, that HTML/Javascript knowledge (at least at the time) was slim in the team, so anything they could do through engines and the client was a far better option.
I want a web profile. But that's a separate feature unrelated to deep linking access to Client screens. This is how software development works.
<<This is how software development works>>
🤣🤣🤣
i have a computer science degree. i've been working in the field for over 30 years.
i think i understand "how software development works".
It's not apparent from your statements at least.
This was a "Deep linking to screens" feature. It was not a "Make the profile available everywhere to everyone" feature. If you've got 30 years experience, you should know better and quit scope creeping like a bad client.
🤣🤣🤣
ALL clients scope cre ep. If you had any experience, you'd know that. it's why i charge by the hour.
Also, please stop claiming you have internal knowledge about what the original feature entailed, and what is and is not in scope. you have no idea. you don't work for Niantic.
Don't want to enter the discussion, but a small clarification: The problem is that Chrome doesn't open an app when opening a link via the address bar. Chrome does open a link via an app when you tap on it while it's embedded in a Website, which is what Reddit does.
What Niantic could do is design a simple landing page for now that, instead of redirecting you to Ingress.com (assuming the link wouldn't be broken), it would show something like "This link can only be opened with Ingress Prime. >Open in App|>Download Ingress Prime". If you'd then tap on "Open in app", Chrome sees it as "The user specifically opened the link, lemme see if there is an App that can be opened" and would open Ingress.
Chrome does open a link via an app when you tap on it while it's embedded in a Website, which is what Reddit does.
So does Ingress. That's already described above. If you paste the link into Telegram for example, then click on it, it opens. That's not what the whining was about though.
Going by the past comments on how Reddit archives the same thing, it seems that way through.
The issue is the feature is working as designed, but someone doesn't agree with the design, but its far from useless.....
https://link.ingress.com/?link=https%3A%2F%2Fintel.ingress.com%2Fagent%2FGorillaSapiens&apn=com.nianticproject.ingress&isi=576505181&ibi=com.google.ingress&ifl=https%3A%2F%2Fapps.apple.com%2Fapp%2Fingress%2Fid576505181&ofl=https%3A%2F%2Fwww.ingress.com%2F
it could be far more useful than it is.
is quibbling over whether this is a "bug" or a "feature request" a productive use of our time?
Literally yes.
If you want a web profile, sign on to the post I made or make your own. New feature, new post, new discussion. Attacking the developers for "failing" or making "broken features" has zero effect except to tell them to ignore you.
So if I have to spend my time teaching you what you should have already learned from 30 years in software development, it's a productive use of my time (assuming you learn).
<<If you want a web profile, sign on to the post I made or make your own.>>
what are you talking about? Web profile? "sign on to the post you made"? srsly, what are you talking about? no srsly, what are you talking about?
re: you teaching me a lesson. 🤣🤣🤣
another thing i've learned after 30 years. harping on the exact language someone uses when pointing out deficiencies in a product is an utter waste of time. grow some skin already. a good software engineer will look past that, see what problems the client has, and work the problem. attacking your client just loses you clients. (in case you missed it, we the players are the client in this case).
and clients attacking other clients for pointing out deficiencies? well that's just Stockholm Syndrome.
Reposting from earlier up the thread: