I've been doing some reading on resolutions a while back and decided 1000*680 was the ideal resolution for us to develop on. But, when publishing and viewing the HTML output at 1000*680, everything looks blurry, even the fonts.
I got the advice to lock the player at optimal size, which indeed showed everything crisp, but we don't want to do that to avoid other issues.
So why not developing at double size? I tried it and it looks great. Performance testing did not show great differences so far. But I never came across someone who developed at 2000 px, even 1000 seems to be an exception. Why is that?
So I came up with the idea of developing at a very high resolution (2000*1360), which seems to work (for now). But before changing everything, I just wanted to get some community ideas about that approach.
3 Replies
Hi Lien!
I'll defer to the community on opinions and why they choose certain things during development.
If you are having difficulty with a file you would like for us to take a look at though, I would encourage you to share.
Thanks Leslie for reply'ing. I opened a case (#00911044) and got the advise to set the player to lock at optimal size: http://www.articulate.com/support/storyline-2/objects-are-blurry-or-pixelated-in-html5-content-sl2 I do not want to do that, as our users have different browser resolutions and I want to offer a flexible solution for them. I don't like scroll bars appearing.
So I came up with the idea of developing at a very high resolution (2000*1360), which seems to work (for now). But before changing everything, I just wanted to get some community ideas about that approach.
Perfect Lien. Thanks for updating me on your process and that you worked with support.
Hopefully the community will be able to chime in and share ideas with you :)
This discussion is closed. You can start a new discussion or contact Articulate Support.