-
-
Notifications
You must be signed in to change notification settings - Fork 115
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
JRE-friendlier download page #766
Comments
Hi, A first step could be to remove the default filter by "Package Type" and set the selector to "Any". (your point 2) Regarding the point 1, the home page has only one big button, it may be strange to have 2 links into the same big button. |
We have just released some new features, you should be able to have a direct link to JRE, for the OS and arch you want, and bookmark it: e.g. Let me know if it's a good solution or if we have to brainstorm a little 😄 Xavier |
Hi @xavierfacq, Although if you went with (unnumbered) option 3 in my initial post – a separate "Download JRE" landing page akin to the current "Download JDK" homepage, it would be even nicer. It could be accessible under https://adoptium.net/jre/, for example. |
Is your feature request related to a problem? Please describe.
The process of downloading JRE (not JDK) from Adoptium currently seems overly complicated, because you have to:
Furthermore, there is no obvious way to even link to the download page with JRE downloads initially visible.
Describe the solution you'd like
A couple simple ideas to make this user experience better:
A slightly more complex solution: build a simple landing page for downloading JRE specifically. Something akin to java.com, but less corporate and friendlier to end-users. In fact, your current home page is pretty much that already, except it points to JDK and not JRE.
Additional context
I'm raising this because I couldn't find an end-user friendly JRE download page that the application developers could link their users to. Java.com still offers version 8, and your "Latest Releases" page just looks overly complicated from an end-user perspective.
The text was updated successfully, but these errors were encountered: