[HN Gopher] Shots: Create Mockups
___________________________________________________________________
Shots: Create Mockups
Author : stefankuehnel
Score : 55 points
Date : 2024-01-19 19:25 UTC (3 hours ago)
(HTM) web link (shots.so)
(TXT) w3m dump (shots.so)
| hemloc_io wrote:
| Saw that you guys support Arc browser, but every time you open
| the sidebar it saves the screenshot !
| wild_egg wrote:
| Full screen overlay on mobile is pretty hostile
|
| I'm not even allowed to read about whatever this service might be
| without going home and getting out my laptop?
| david422 wrote:
| It's all about browser screen size apparently. Anything less
| than 1080px width and you will still get the same "Shots mobile
| is coming" message.
| iinnPP wrote:
| This made it an instant no from me. Doesn't even allow desktop
| mode.
| petepete wrote:
| Yeah, even if it's great my interest has waned.
| jitl wrote:
| (I work at Notion)
|
| I usually feel a bit apprehensive when I see a new app pop up
| using the .so TLD (Somalia, operated by SONIC.so), since we've
| faced a lot of issues with it over the years. I end up repeating
| the same kind of comment about it (eg
| https://news.ycombinator.com/item?id=36825966), but I wonder if
| all the apps on it, including Notion, have changed the reputation
| of it with corporate firewalls by now.
|
| Still, watch out if you host user-generated content there, it can
| be hard to undo reputation damage to .so domains if you get
| reported to various watchdogs. Notion's longest hard-down outage
| happened after a takedown notice got sent to one of our upstream
| providers but they never forwarded it to us, and it took ling
| hours on the phone to various NICs and ISPs to get unblocked.
| stickfigure wrote:
| Also - the organizations that run the DNS servers of little top
| level domains are not necessarily competent. Back when I had a
| company on the .st domain, we had an 8-hour outage when
| something in the TLD infrastructure broke and their support
| team was asleep:
|
| https://github.com/stickfigure/blog/wiki/Beware-cutesy-two-l...
| jitl wrote:
| Yeah, this reminds me of our outage. When we finally got
| through to SoNIC at 2am their time, and they scrambled to
| find someone who could speak English, and we scrambled to
| find someone who could speak French. I think with high school
| level on either side plus Google Translate, eventually we
| worked out the issue was with an intermediary in Germany.
| dinkleberg wrote:
| Not the OP, but thanks for the heads up!
|
| Just recently started a new project with a .so domain, but
| looks like I'll have to pick up another one. No point
| introducing more work for ourselves just for a domain name.
| tiffanyh wrote:
| Why doesn't Notion use .com (since you now own notion.com)?
| jitl wrote:
| Our public API uses Notion.com:
| https://developers.notion.com/
|
| Switching the product and marketing sites would take a lot of
| work for unclear/low benefit since at this point we've
| learned the .so lessons and have a good reputation.
|
| Given the choice of projects like "scale infra so we stay
| online and fast-ish", "improve search", or "notion dot com",
| Notion dot com ends up below the cut line.
| pantsforbirds wrote:
| I lost access to all of our documentation at work for a week
| because my (small local) ISP banned all content from Somalia as
| being suspicious. I had to call their office and explain to
| them that Notion is a rather large and popular application.
| jitl wrote:
| Thanks for your help and sorry for the trouble!
| orenlindsey wrote:
| "Safari is not supported yet"
|
| Is Safari really that hard to develop for? Name one feature this
| site needs that won't run in safari. WebKit has been getting a
| lot better recently, I feel like not supporting Safari at this
| point is because of one of three things: you're too lazy to try
| it, don't have a Mac, or you are stuck to the opinion that Safari
| is somehow behind Chrome or Firefox in major ways.
|
| I use safari daily and *never* have a problem with a site not
| working. Ever. So I doubt there's some new web api that this site
| needs that doesn't work on Safari.
| ororroro wrote:
| That is odd because all the mockup devices are Apple.
| seaal wrote:
| After switching user agents to Chrome and trying it out, I ran
| into a problem pretty quick. The dynamically generated "Magic"
| backgrounds use SVGs with the 'filter: blur' style which isn't
| working properly despite it being supported by Safari [1]
|
| Most of the features work fine though. Website does state that
| it's in beta as well.
|
| What do you have against using another browser?
|
| [1] https://caniuse.com/svg-filters
| Nevermark wrote:
| > What do you have against using another browser?
|
| Someone doesn't have to have anything against other browsers
| to prefer using their favorite browser without futzing around
| with browser-site combinations.
|
| Also, web developers here are interested in any reports of
| cross platform problems, so they can avoid requiring their
| users to futz around.
| jwells89 wrote:
| > Someone doesn't have to have anything against other
| browsers to prefer using their favorite browser without
| futzing around with browser-site combinations.
|
| Yes, this is irritating. If I encounter a site/app with
| browser requirements, I'm going to find an alternative to
| that site/app, not use a different browser.
| ubertaco wrote:
| It's been a few years since I did frontend dev, but Safari was
| _absolutely_ the most difficult browser we had to develop for,
| _especially_ on iOS.
|
| With IE, you can polyfill missing APIs. With Safari, you have
| to put in extra work to ensure your polyfills override Safari's
| built-in implementations in all sorts of exciting ways based on
| which particular Safari version someone is running, because
| it's _obnoxiously_ common for Safari to have broken or
| incomplete implementations of web APIs. So if you're just
| checking for the presence of some particular global, it'll be
| there...but it'll be subtly broken in various ways. We had
| constant issues with Safari's implementations of LocalStorage
| and IndexedDB, and with its weird tendency to "ghost-hover"
| over elements after a completely different element in the page
| was tapped/clicked, and that's just what's off the top of my
| head from when I last did frontend dev consistently (about 7ish
| years ago).
|
| The only way to repro any of Safari's weird bugs nonsense, of
| course, was to shell out for a Mac or iOS device. You can't
| repro any Safari issues on any other, less-expensive platform.
| It's classic Oracle-style vendor lock-in with their vertically-
| walled-off tooling and lack of test images.
|
| Except at least Oracle never put out a constantly-broken
| browser, let alone one that had -- and still has -- monopoly
| capture of an entire platform.
|
| If you've got a desktop Firefox or Chrome issue, you can launch
| Firefox or Chrome on a cheap Linux or Windows machine or VM and
| repro it, and then snapshot the VM for reproducibility.
|
| If you've got a mobile Firefox or Chrome issue, you can launch
| Firefox or Chrome on a cheap android device (or emulator), and
| if for some reason it really truly proves to be something
| Google or Mozilla hasn't implemented correctly _and_ you can't
| polyfill it...then you can advise users to try a different
| browser as a workaround.
|
| There _is no_ "different browser" on iOS. If Apple has screwed
| up yet another standard web API, your users are hosed unless
| you can get really creative at dancing around their broken pile
| of crap.
| me_bx wrote:
| Here are some Safari-specific issues I have met when developing
| a website in the past two years: * font being
| displayed way bigger than in the other browsers - had to add
| normalization rules specific of Safari * Parsing dates in
| the format "YYYY-MM-DD HH:MI:SS" not working, had to convert to
| ISO-8601 using a regex (the dates in original format were
| received from a third-party website). * Interactions in
| maps not working using leaflet library (version 1.7 at the
| time). Fixed by switching to maplibre, which turned out to be a
| great move for other reasons. * HTML in SVGs (via
| ForeignObject) are always displayed on top of the SVG content,
| making it impossible to annotate HTML with SVG markup (arrows,
| circling stuff).
|
| Plus some issues with `backdrop-filter:blur`, although this CSS
| is also problematic elsewhere.
|
| All in all, it felt like having to deal with Internet Explorer
| 10+ years ago: the other browsers work well out of the box, and
| tricks and workarounds need to be identified for the bad
| browser.
| dinkleberg wrote:
| This is a beautiful app, well done!
| shadeslayer_ wrote:
| The site loads like I'm on a dial-up connection but I'm actually
| on a 300Mbps fiber line. Pass.
___________________________________________________________________
(page generated 2024-01-19 23:00 UTC)