Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consistently use *applications* or *apps* #42

Closed
philippederyck opened this issue Mar 24, 2024 · 1 comment
Closed

Consistently use *applications* or *apps* #42

philippederyck opened this issue Mar 24, 2024 · 1 comment

Comments

@philippederyck
Copy link
Contributor

philippederyck commented Mar 24, 2024

In his review, Justin Richer pointed out that the spec inconsistently uses both the term applications and apps in the title and the document. It makes sense to settle for one and be consistent about it.

My vote goes to applications, which is most common in the context of web applications. Apps is more related to native/mobile apps.

A quick Google search on Angular apps vs Angular applications or js apps vs js applications also indicates that applications is more common.

When not updating, include applications vs apps in the terminology section.

@aaronpk
Copy link
Member

aaronpk commented Mar 26, 2024

+1 for "applications"

philippederyck added a commit to philippederyck/OAUTHWG-oauth-browser-based-apps that referenced this issue Apr 11, 2024
Resolve issue oauth-wg#42 by consistently using applications.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants