Talk:MobileIron
| This is the talk page for discussing improvements to the MobileIron article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article was nominated for deletion on July 25 2013. The result of the discussion was delete. |
 | This article has not yet been rated on Wikipedia's content assessment scale. |
 | The Wikimedia Foundation's Terms of Use require that editors disclose their "employer, client, and affiliation" with respect to any paid contribution; see WP:PAID. For advice about reviewing paid contributions, see WP:COIRESPONSE. |
Some proposed changes
edit | This edit request by an editor with a conflict of interest has now been answered. |
Information to be added:
1. Please expand the infobox with the details given below:
2. Also, please add this image - https://commons.wikimedia.org/wiki/File:MobileIron_Headquarters.png - in the body of the page.
Explanation of the issue: Requesting to expand the infobox with information found online and adding images found on Wikimedia Commons. All URLs are given above with the text. Thanks.
TP495 (talk) 17:16, 20 August 2019 (UTC)
Reply 20-AUG-2019
edit
Edit request implemented Spintendo 22:43, 20 August 2019 (UTC)
Proposing a few more changes
edit | This edit request by an editor with a conflict of interest was declined. See below for additional information about this request. |
Information to be added:
1. Please add a section named 'Technology'
Extended content
|
|---|
|
Unlike single sign on which still requires a username & password, zero sign-on enables passwordless mobile authentication to log into web apps from any desktop – managed or unmanaged. Unmanaged devices are completely controlled by the user with little or no visibility to the service provider. When a user, with Access set up on their mobile device, logs into an enterprise web app using an unmanaged desktop, Access displays a web page with a QR code instead of a username and password field. The user then uses their mobile device and authenticates to their MobileIron client via biometrics, and then uses the app to scan the QR code in the browser to gain access to the web app on the unmanaged device.[1] 2. Please add a section named 'Recognition' During the five-year period of 2009-2013 MobileIron was named the fastest growing technology company in the world and ranked #1 in Deloitte’s Fast 500 Index.[2] The company was positioned as a Leader in Gartner’s Magic Quadrant for Mobile Device Management Software in 2011,[3] 2012[4] and 2013.[5] It was positioned as a Leader in Gartner’s Magic Quadrant for Enterprise Mobility Management Suites from 2014[6] to 2017.[7] It was also positioned as a Leader in Gartner’s Magic Quadrant for Unified Endpoint Management Tools in 2018[8] and 2019.[9] MobileIron was named a Leader in the 2018 Forrester Wave for Unified Endpoint Management[10] and the 2018 IDC MarketScape for Unified Endpoint Management Software.[11] Explanation of the issue: Requesting to add information (if possible) with references found online. All URLs given along with the text. Thanks. References
|
TP495 (talk) 18:04, 27 August 2019 (UTC)
Reply 27-AUG-2019
edit
Edit request declined
- Wikipedia is not an instruction manual on how to use this technology, per WP:NOTMANUAL.
- By their very nature, accolades can be subjective — in that they represent a very specific point of view — the point of view of the individual or organization which determines who receives the accolade and why. To counter this, a good practice is to limit the listing of accolades to only those which are independently notable in Wikipedia.[a]
- To include a list of accolades here, please ensure that only accolades which are independently notable in Wikipedia are listed in the request.[b]
Regards, Spintendo 01:25, 28 August 2019 (UTC)
Notes
- ^ An accolade which is independently notable is recognized by having its own article in Wikipedia.
- ^ The requirement I'm asking for here that the accolades be notable is not due to WP:N (which is not a content requirement). My asking for notability here is to ensure WP:NPOV. The adding of several points of view to an article in the form of an accolades section may skew the article's balance.[1] Thus, my own practice is to limit the listing of accolades to only those which are independently notable in Wikipedia.
References
- ^ "WP:BALANCE". Wikipedia. 20 July 2019.
...articles should not give minority views or aspects as much of or as detailed a description as more widely held views or widely supported aspects.
Proposing some changes
edit| | Part of an edit requested by an editor with a conflict of interest has been implemented. Please see the reply section below for additional information about this request. |
Information to be added:
Edit request
|
|---|
|
1. Please edit the first paragraph from MobileIron Inc. is an American software company specializing in security for mobile devices, apps, and cloud services, including enterprise mobility management (EMM) and mobile device management (MDM). to: MobileIron Inc. is an American software company specializing in enterprise security for mobile devices, apps, and cloud services, through Unified Endpoint Management (UEM), enterprise mobility management (EMM) and mobile device management (MDM). MobileIron offers zero trust technologies such as zero sign-on (ZSO) user and device authentication, multi-factor authentication (MFA), and mobile threat defense (MTD).
2. In the 'History' section, please add the following referenced information It became publicly traded in 2014[1] on NASDAQ under the ticker MOBL.[2] In 2017, the company started providing IoT management under the leadership of Barry Mainz.[1] Simon Biddiscombe was appointed CEO in October 2017.[3] In January 2018, MobileIron partnered with Google Cloud to distribute Google apps through MobileIron’s EMM platform and provide a secure enterprise applications and services portal.[4]
MobileIron's software also has mobile threat defense tools to combat vulnerabilities & malware. MobileIron launched Access in 2016, bringing EMM together with identity management and restricting authentication to known apps and devices. Authentication could also be restricted by other device compliance policies.[5] In 2017, MobileIron developed a zero sign-on enterprise by enabling zero sign-on to cloud services on managed devices with its Access product. In 2019, MobileIron extended that capability by making passwordless access to cloud services available from any iOS device, managed or unmanaged, using the mobile device as the user’s secure ID.[6] According to Fast Company, MobileIron is “at the leading edge of the shift away from passwords,” highlighting its mobile-first and mobile-always-available approach to authentication.[7] Explanation of the issue: Requesting to update information in History and Products section by adding data found online. All URLs given along with the text. Thanks. References
|
TP495 (talk) 15:42, 13 September 2019 (UTC)
Reply 13-SEP-2019
edit Edit request partially implemented
The lead section was not implemented, as the terms used there, such as mobile device management (MDM), zero trust technologies, zero sign-on (ZSO) user and device authentication, multi-factor authentication (MFA), and mobile threat defense (MTD) have not been Wikilinked.
The information concerning the NASDAQ ticker symbol is already included in the infobox.- Information on IoT management was not added, as it was referenced by TechCrunch.
- Information on the appointment of the CEO in 2017 is already in the article.
Information on the Google Cloud partnership was added.- Information on Access was not added because it was referenced by BrianMadden.com, which offers opinion/editorial content.
- Information on the zero sign-on enterprise was not added, because it was referenced by a Forbes.com contributor.
- Information provided by Fast Company was not added, as it does not conform with WP:BALANCE (e.g.,
"at the leading edge"
).[a]
Regards, Spintendo 17:33, 13 September 2019 (UTC)
Notes
- ^ As other views of this company have not been included regarding their "shift away from passwords", this would be the only viewpoint given.
- @Spintendo: - Thanks for the partial implementation and appreciate your guidance. TP495 (talk) 15:00, 16 September 2019 (UTC)
Proposing changes to lead paragraph
edit| | This edit request by an editor with a conflict of interest has now been answered. |
Information to be edited:
Please change the first paragraph from
MobileIron Inc. is an American software company specializing in security for mobile devices, apps, and cloud services, including enterprise mobility management (EMM) and mobile device management (MDM).
to:
MobileIron Inc. is an American software company specializing in enterprise security for mobile devices, apps, and cloud services, through Unified Endpoint Management (UEM), Enterprise Mobility Management (EMM) and Mobile Device Management (MDM). MobileIron offers zero trust technologies such as multi-factor authentication (MFA).
Explanation of the issue: Addressing the Wikilinks as suggested by the moderator - Spintendo in the previous edit request. Thanks. TP495 (talk) 15:07, 16 September 2019 (UTC)
Reply 16-SEP-2019
edit Edit request implemented
- "Zero trust technologies" was not wikilinked, so it was not added. As MFA was mentioned (and since MFA is part and parcel of the company's provision of MDM), these two sentences were combined. That being said, if it's true that these two things are very different, then a suggestion would be appreciated on how to combine the two sentences without using the generic "they also provide MFA." This dilemma on how to structure the lead section is shown below:[a]
| Lead sentence No. 1 Main components |
Lead sentence No. 2 Main components |
|---|---|
| Company provides UEM, EMM and MDM | MobileIron offers |
If there is some other way of combining these two elements without implying anything incorrect, please advise.[c] Regards, Spintendo 23:28, 16 September 2019 (UTC)
Notes
- ^ The dilemma only exists if the COI editor finds fault with the implemented lead section (which they might). If they do not, then this part of my reply may be ignored.
- ^ The phrase "such as" was re-used to connect the two sentences. If this re-use is incorrect, then the dilemma spelled out here comes into play. If it's ok to use, then there is no dilemma — and this part of my reply may be ignored.
- ^ As an alternative, the entire proposed claim as originally written could be implemented (albeit in abbreviated form) so long as the phrase zero trust technologies was Wikilinked.