Talk:Here WeGo

This page should not be speedy deleted because...

The app has over 1 million downloads.

it is an app and it deserves its own Wikipedia article. see here for iOS version https://itunes.apple.com/us/app/here-offline-navigation-maps/id955837609?mt=8

and a blog article on its release for Android: http://360.here.com/2014/12/10/android-now-available-free-google-play/

it will take some time to get the formatting correct of the article, but i believe it should not be deleted because it is a relevant app just like Periscope or any other app is.

it is a legitimate app if u check the references, and it will take a bit of a time to build up the content of the page, but it shouldn't be deleted. Also how will i know if u are not going to delete it? --Adrianhughes1998 (talk) 16:02, 29 June 2015 (UTC)

i have already detailed the reasons for non-deletion of this page previously. This is an actual app that is used by millions of users on three smartphone platforms, and is such an important gateway for users to know the app. Other apps such as Google apps or Apple Music aren't deleted, so why should HERE be deleted.  — Preceding unsigned comment added by Adrianhughes1998 (talk • contribs) 12:40, 25 August 2015 (UTC) 

This page should not be speedily deleted because... it is a legitimate app if u check the references, and it will take a bit of a time to build up the content of the page, but it shouldn't be deleted. Also how will i know if u are not going to delete it? --Adrianhughes1998 (talk) 16:02, 29 June 2015 (UTC)

This page should not be speedily deleted because... i have already detailed the reasons for non-deletion of this page previously. This is an actual app that is used by millions of users on three smartphone platforms, and is such an important gateway for users to know the app. Other apps such as Google apps or Apple Music aren't deleted, so why should HERE be deleted. — Preceding unsigned comment added by Adrianhughes1998 (talk • contribs) 12:40, 25 August 2015 (UTC)

Merge proposal of app article

I am proposing this article to be merged into Here (company). I don't feel like it should have a seperate article, and I believe it would fit good in the company article, particularly after its sale from Nokia. Give your opinions. --G&CP (talk) 22:28, 4 January 2016 (UTC)

I am the one who originally created the separate "HERE (app)" page. I believe it should not be part of the company article, because even though they are directly related and tied in together, the HERE app is substantial on its own. The main HERE article also contains a lot of information on their company's mapping/liaison/technology aspects and is long enough as it is. I only feel that it would become lost if it was absorbed into the main HERE article. Adrianhughes1998 (talk) 00:35, 15 January 2016 (UTC)

Also you will see that if you check something like Google Maps on Wikipedia, this has its own page under "Google Maps". Therefore I have moved the HERE (app) page to be HERE Maps (app), in line with the recent official branding changes. This change is also reflected in the Google Play and iOS App Store entries respectively for these apps.Adrianhughes1998 (talk) 12:27, 15 January 2016 (UTC)

About use of OpenStreetMap...

There are some indication aobout HERE's reuse of OpenStreetMap information? --Krauss (talk) 13:14, 1 February 2016 (UTC)

External links modified

Hello fellow Wikipedians,

I have just added archive links to one external link on HERE Maps (app). Please take a moment to review my edit. If necessary, add {{cbignore}} after the link to keep me from modifying it. Alternatively, you can add {{nobots|deny=InternetArchiveBot}} to keep me off the page altogether. I made the following changes:

• Added archive http://web.archive.org/web/20150427111527/http://www.nokia.com/za-en/support/faq/?action=singleFAQ&caseid=FA133108_en_US to http://www.nokia.com/za-en/support/faq/?action=singleFAQ&caseid=FA133108_en_US

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

• If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
• If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—^{cyberbot II}_{Talk to my owner:Online} 20:47, 26 February 2016 (UTC)

Capitalization

Why does it say "HERE" everywhere in the article, while the official logo obvoiously spells it "here"? --BjKa (talk) 21:18, 3 April 2016 (UTC)

@BjKa: The company insists on stylizing it that way. However, we should not. ViperSnake151  Talk  22:38, 27 July 2016 (UTC)

I have no problem with Wikipedia having its own rules and not complying with corporations' wishes, but I don't see a reason for an all-cap-spelling. "Here" is not an acronym, but intended to be pronounced as a word.

Maybe when quoting rules in other users faces, you should make sure first, that you've read them yourself properly. Search for the line that says "avoid: TIME, KISS, ASUS"

--BjKa (talk) 15:03, 3 August 2016 (UTC)

What is Software Testing Life cycle ?

Software is an integral part of our lives, from the apps on our smartphones to the programs running our computers. However, no software is perfect from the moment it's created, and this is where the Software Testing Life Cycle (STLC) comes into play. STLC is a systematic process that ensures the quality and reliability of software by identifying and rectifying defects and issues. In this Wikipedia article, we will explore the various phases of the Software Testing Life Cycle. Definition: The Software Testing Life Cycle (STLC) is a systematic and structured approach to ensure the quality and reliability of software by verifying its functionality, performance, and other essential attributes. STLC consists of several phases, each serving a specific purpose in the testing process. Phases of the Software Testing Life Cycle (STLC): Requirement Analysis: The first phase involves understanding and analyzing the project requirements and defining the scope of testing. It is essential to have a clear understanding of what the software should do before testing begins. Test Planning: In this phase, the test strategy and test plan are developed. The strategy outlines the overall approach to testing, while the test plan details specific test cases, resources, and schedules. Test Design: During this phase, test cases and test data are designed, keeping in mind the requirements and test objectives. The test cases serve as a blueprint for the testing process. Test Environment Setup: The test environment, which mirrors the production environment, is set up with the necessary hardware, software, and network configurations. Test Execution: This is where the actual testing takes place. Testers execute the test cases, record test results, and report any defects they encounter. Different types of testing, such as functional, performance, security, and usability testing, may be conducted during this phase. Defect Reporting and Tracking: Any defects or issues identified during test execution are reported in a defect tracking system. These issues are tracked until they are resolved and the software is considered bug-free. Regression Testing: After defects are fixed, regression testing is performed to ensure that the changes made to the code do not introduce new issues. This phase helps maintain the stability of the software. Test Closure: Once all testing phases are complete and the software meets the predefined criteria, a test closure report is generated. This report summarizes the testing activities and outcomes. Post-release Maintenance: Even after the software is released, testing activities may continue in the form of post-release maintenance. This is done to ensure that the software continues to function correctly as it is used in the real world. Benefits of the Software Testing Life Cycle (STLC): STLC offers several benefits, including: Improved Quality: STLC helps identify and rectify defects early in the development process, leading to higher-quality software. Reduced Costs: Finding and fixing defects early in the development cycle is more cost-effective than addressing them later. Enhanced Customer Satisfaction: Testing ensures that the software meets the customer's expectations, resulting in higher satisfaction. Reliable Software: By following a structured testing process, software reliability is significantly improved. Conclusion: The Software Testing Life Cycle (STLC) is an integral part of software development, ensuring the quality and reliability of software applications. By following a structured and systematic approach, software testing helps in identifying and rectifying defects and issues early in the development process. This results in higher-quality software, reduced costs, and increased customer satisfaction. STLC is an essential practice for delivering software that meets and exceeds user expectations. Agicon Solutions (talk) 06:03, 20 October 2023 (UTC)