You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assumed this, like all the other "cool new browsers" from the past few years was an Apple exclusive because your are only showing screenshots that look to be running on OSX.
I've been making Cross-platform Desktop Apps for years and have always found that Windows users dominate downloads of desktop apps. Even for software development tools, it's still 70+%.
It's very important to make a good first impression and say "We care about you, and have taken the time to customize the website to cater to you, yes, our developers use your OS and manually test things there, you are not an after-thought". The website's goal is mostly just marketing and giving people the download link. Marketing works better when it's targeted.
You can use the UserAgent to make an educated guess as to what OS/Arch the user has and present that as the default link too. Obviously, you'd still have an "Other Downloads" or "More Downloads" button next to it.
UAParser().withClientHints().then((result)=>{constCPU=result.cpu.architecture;// 'arm64', 'amd64', 'ia32', etc.constOS=result.os.name;// 'Windows', 'Ubuntu', 'Android', 'MacOS', etcif(OS==='Windows'){// Show Windows screenshots/videosif(CPU==='arm64'){// Show Windows arm download}else{// Show Windows 86/64 download}}else{// ...}});
This does require you to create matching screenshots on each OS, but honestly if you aren't willing to do that, then I don't trust that you are actually manually testing this browser in those OS's anyways. So I also have to assume your app is a buggy mess on those platforms. Perception matters.
A trick I've used before is adding classes to the <html> tag and using CSS to show/hide elements based on the UA. Browsers skip downloading images until they are displayed.
<imgsrc="/static/images/hero-win.png" alt="MyApp on Windows" class="windows"><imgsrc="/static/images/hero-lin.png" alt="MyApp on Linux" class="linux"><imgsrc="/static/images/hero-lin.png" alt="MyApp on MacOS" class="macos">
<!-- Smart defaults for the download buttons --><ahref="/downloads.html" class="btn" id="download-button"><imgid="download-icon" src="/static/images/down-arrow.svg" aria-hidden><spanid="download-text>Download</span></a><a href="/downloads.html" class="btn">All Download Options</a>
// Some dummy vanilla JS to demonstrate changing the buttons after the UA is detected.constdownloadButton=document.getElementById('download-button');constdownloadIcon=document.getElementById('download-icon');constdownloadText=document.getElementById('download-text');downloadButton.href='/downloads/my-app-v1.0.0-'+OS+'-'+ARCH+'.'+fileExtension;downloadIcon.src='/static/images/os-logo-'+OS+'.svg';downloadText.innerText=OS+' Download';
The text was updated successfully, but these errors were encountered:
I assumed this, like all the other "cool new browsers" from the past few years was an Apple exclusive because your are only showing screenshots that look to be running on OSX.
I've been making Cross-platform Desktop Apps for years and have always found that Windows users dominate downloads of desktop apps. Even for software development tools, it's still 70+%.
It's very important to make a good first impression and say "We care about you, and have taken the time to customize the website to cater to you, yes, our developers use your OS and manually test things there, you are not an after-thought". The website's goal is mostly just marketing and giving people the download link. Marketing works better when it's targeted.
You can use the UserAgent to make an educated guess as to what OS/Arch the user has and present that as the default link too. Obviously, you'd still have an "Other Downloads" or "More Downloads" button next to it.
This does require you to create matching screenshots on each OS, but honestly if you aren't willing to do that, then I don't trust that you are actually manually testing this browser in those OS's anyways. So I also have to assume your app is a buggy mess on those platforms. Perception matters.
A trick I've used before is adding classes to the
<html>tag and using CSS to show/hide elements based on the UA. Browsers skip downloading images until they are displayed.The text was updated successfully, but these errors were encountered: