Except the choice of using another brand of computer.
Sketch: Proud to Build a Truly Native Mac App
251–260 of 362 posts
Re: Sketch: Proud to Build a Truly Native Mac App
#252Earlier quoted context omitted.
Yes, functional spyware with broken UI. A dark mode explorer window is drawn in light mode for a split second and then painted black. It's ridiculous.
That's not true on current Win10, I've never seen it before. What build are you using? Are you connected over RDP or something?
Re: Sketch: Proud to Build a Truly Native Mac App
#253> For us, the ultimate benefit of being a native macOS app is that it puts the choice in your hands. Except the choice of using another brand of computer.
Re: Sketch: Proud to Build a Truly Native Mac App
#254Earlier quoted context omitted.
It’s snappy for a web app. If it was a native app it would be mediocre.
the thing with web apps is - it's slow, but it is the Java's original goal from the 90s "write once, run everywhere" actually realized. Plus, built-in collaborativeness and automatic updates. And, easier to get developers. Native is nice, native is fast, and it will have its place (compare how bad is Google Meet compared to Zoom with respect to CPU/RAM), but web is becoming "good enough".
thats rarely true for complex web apps... (doubly true if your using firefox)
Re: Sketch: Proud to Build a Truly Native Mac App
#255Earlier quoted context omitted.
Swing is definitely not "less native" than Electron. The entire window is a web view in Electron apps. I believe Java Swing was even an officially supported UI toolkit on the Mac a long time ago.
The menus in Swing aren't native but are in Electron.
Simple experimental proof: resize the window to be very small, and open a menu. The menu can't go outside the bounds of the window.
Re: Sketch: Proud to Build a Truly Native Mac App
#256Earlier quoted context omitted.
Not really. I could switch to Figma from Sketch very easily because I could upload my Sketch files in Figma and Figma could deconstruct them into layers and elements with even layer names intact! Vice versa? No. Even Photoshop files .PSD are readable in many other photo editing apps. Figma.. no never.
I thought “if you’re in the EU, make a GDPR request for your data”. However, the only page I found is https://help.figma.com/hc/en-us/articles/360041060434-Genera... , which says they’re committed to your privacy, but doesn’t mention data portability.
Re: Sketch: Proud to Build a Truly Native Mac App
#257Earlier quoted context omitted.
I think the killer feature of macs with Apple Silicon is that the iPad versions of Slack and Discord would "just work" and people wouldn't have to deal with Electron crap anymore.
I’ll believe the story that these will be any good when Catalyst apps will start behaving like native apps. If developers can’t bother making a native experience with frameworks that are meant to do this, I don’t think they will with an even simpler paradigm. My canary in the coal mine: Apple’s own SF Symbols.
intuitively, it would seem apples answer is to make mac apps behave/look like ipad/catalyst appe (e.g big sur's uo redesign)
Re: Sketch: Proud to Build a Truly Native Mac App
#258Earlier quoted context omitted.
figma is pretty freaken amazing, and it works outside of macs. So overall there is nothing but upsides to it. Collaboration is amazing too. Just... No down sides.
Fan of Figma, but would switch to a better one in a heartbeat because of the following huge downside.. Once you are in Figma, you are trapped forever. No way to get out your original editable artwork files. Buyer beware!
Re: Sketch: Proud to Build a Truly Native Mac App
#259Earlier quoted context omitted.
I’m not sure I would feel sorry for them; doubling down on your one-platform stance while your customers are overwhelmingly voting with their feet and wallets for cross-platform support is just stupidity in my opinion. They’ll have a core set of customers who will appreciate it, but I’m not sure they’re going to pay the bills just because you’ve convinced them stay, which they probably would’ve done anyway
It might also be that they have considered the cross-platform option...and found it not feasible. They might have decided that it is easier to continue on the current path.
Maybe decision makers at Sketch were looking at stats like majority of designers use MacOS - while that's probably true, that's not the case for devs, product people etc - who are now all using Figma to a degree too. Once you've got that cross-team use of the same app, you're not going to want to go back.
Re: Sketch: Proud to Build a Truly Native Mac App
#260I find at least zooming in/out large project files to be much faster in Figma. Lack of good offline workflow sucks but the overall features and cross-compatibility means nearly everyone is moving to Figma. Sketch isn’t bad software at all, but they are really losing out to the network effects of Figma. Design software isn’t like IDEs where everyone in an organisation can use their favourite one - orgs choose design t…
This has just been solved: https://www.figma.com/blog/behind-the-feature-autosave/
Interesting timing on these articles getting published. Almost at exactly the same time, and almost polar opposites.