5 ms·

What can Sketch do that Figma can't?

by Scarbutt 6y ago

geerlingguy 6y ago
Run natively on the Mac /s
- EvilEy3 6y ago
  Why /s though? It is a huge pro for some people.
  - geerlingguy 6y ago
    Because it's already been mentioned a number of times in the thread and is a very major selling point (IMO).
usaphp 6y ago
Work offline, Better font rendering
jnymck 6y ago
Custom keyboard shortcuts
Razengan 6y ago
Better support for the built-in accessibility features of macOS.
- jcelerier 6y ago
  I wonder how many people with visual accessibility issues would take a graphic design job
  - saagarjha 6y ago
    Accessibility features are used by people regardless of whether they have visual accessibility issues. For example, I (and many others–watch some WWDC presentations closely and you'll see this) use the "display zoom" feature during presentations and when doing UI work to focus on things. The feature where you wiggle the mouse cursor to make it big? That's an accessibility feature, but it got a prime spot at the keynote when it was announced. I have subtitles enabled all the time since it helps me catch things in videos if I miss what someone said. macOS has text-to-speech, which is quite useful to read me back things I write for grammatical errors or typos. Accessibility features can and are used by everyone. (Disclaimer: I have partial colorblindness and wear glasses.)
    - ChrisMarshallNY 6y ago
      You can use voiceover as a way to add a lot of context and “color” to a UI. I make a big effort to support voiceover in my apps. In fact, most of the text that I translate is never seen by the user[0]. On the Mac, I also like to use tooltips, applying the same string as voiceover. [0] https://github.com/RiftValleySoftware/ambiamara/blob/bbb1d986c654fc23afb4861f87c1bbdc91d7d3ee/Main%20App/Resources/Base.lproj/Localizable.strings#L107 https://github.com/RiftValleySoftware/ambiamara/blob/bbb1d98... (Note, also, that these voiceover strings have been localized in French, German, and Spanish).
    - jcelerier 6y ago
      of all the features you mention, except TTS none depend on the app being written in a specific framework as far as I know ? (and I don't remember TTS not working in e.g. Qt apps for instance - at least I know that I sometimes bash my keyboards repeatedly to stop the damn thing that I opened by whatever goddamn shortcut :D)
      - saagarjha 6y ago
        This was a direct response to your comment, so I was mainly focused on what accessibility features I use. However, one I missed but I use all the time is being able to control applications using accessibility APIs.
  - sjwright 6y ago
    They could certainly take copywriting and proofing jobs.

What can Sketch do that Figma can't?

geerlingguy 6y ago

Run natively on the Mac /s

EvilEy3 6y ago
Why /s though? It is a huge pro for some people.
- geerlingguy 6y ago
  Because it's already been mentioned a number of times in the thread and is a very major selling point (IMO).

usaphp 6y ago

Work offline, Better font rendering

jnymck 6y ago

Custom keyboard shortcuts

Razengan 6y ago

Better support for the built-in accessibility features of macOS.

jcelerier 6y ago
I wonder how many people with visual accessibility issues would take a graphic design job
- saagarjha 6y ago
  Accessibility features are used by people regardless of whether they have visual accessibility issues. For example, I (and many others–watch some WWDC presentations closely and you'll see this) use the "display zoom" feature during presentations and when doing UI work to focus on things. The feature where you wiggle the mouse cursor to make it big? That's an accessibility feature, but it got a prime spot at the keynote when it was announced. I have subtitles enabled all the time since it helps me catch things in videos if I miss what someone said. macOS has text-to-speech, which is quite useful to read me back things I write for grammatical errors or typos. Accessibility features can and are used by everyone. (Disclaimer: I have partial colorblindness and wear glasses.)
  - ChrisMarshallNY 6y ago
    You can use voiceover as a way to add a lot of context and “color” to a UI. I make a big effort to support voiceover in my apps. In fact, most of the text that I translate is never seen by the user[0]. On the Mac, I also like to use tooltips, applying the same string as voiceover. [0] https://github.com/RiftValleySoftware/ambiamara/blob/bbb1d986c654fc23afb4861f87c1bbdc91d7d3ee/Main%20App/Resources/Base.lproj/Localizable.strings#L107 https://github.com/RiftValleySoftware/ambiamara/blob/bbb1d98... (Note, also, that these voiceover strings have been localized in French, German, and Spanish).
  - jcelerier 6y ago
    of all the features you mention, except TTS none depend on the app being written in a specific framework as far as I know ? (and I don't remember TTS not working in e.g. Qt apps for instance - at least I know that I sometimes bash my keyboards repeatedly to stop the damn thing that I opened by whatever goddamn shortcut :D)
    - saagarjha 6y ago
      This was a direct response to your comment, so I was mainly focused on what accessibility features I use. However, one I missed but I use all the time is being able to control applications using accessibility APIs.
- sjwright 6y ago
  They could certainly take copywriting and proofing jobs.