3 ms·

This is accurate. I should have possibly mentioned in more detail that at the time I had a lot of experience with prior apps, so whipping another one together—p

This is accurate. I should have possibly mentioned in more detail that at the time I had a lot of experience with prior apps, so whipping another one together—particularly for such a simple concept—is trivial. I’m surprised anyone here thinks something like Snaplight would take more than an hour to build (no repos, testing on device but otherwise no tests, simple permissions, uncomplicated UI that only improved post-launch, etc.).

Liquid_Fire 7y ago
> I’m surprised anyone here thinks something like Snaplight would take more than an hour to build I think it would take me longer just to make the icon, having never done anything like that before. Think about all the skills you had previously built up that allowed you to make it in an hour. If someone lacks even one of them, they would never be able to do it so quickly.
- giarc 7y ago
  Likely just used some stock icons or had previously designed them for another project and never used them.
  - tannerc 7y ago
    I’m a full-time designer and designed everything in the app from scratch.
    - sizzle 7y ago
      Hi Tanner, big fan of your design portfolio. As a fellow designer, what inspired/motivated you to make the jump into learning how to code? Was it simply scratching the itch to make higher fidelity prototypes? PS- should designers code? ;)
      - tannerc 7y ago
        Thank you for the kind words! I started coding long, long ago in order to build my web portfolio (back before site builders were a thing). As a result I saw how empowering coding can be. I've always felt being able to code software gives you an ability to solve a lot of your own problems with technology. e.g. I have a lot of private tools I've designed and coded to help me in my day job (such as this simple one I recently open sourced: https://tannerchristensen.com/spf https://tannerchristensen.com/spf). If you're a designer who works on digital products, I think it's only advantageous to know some programming. It gives you empathy for your engineering peers, gives you more insight into how what you design will actually get built (and the constraints/advantages of the technology), and helps you see problems in different—often more linear and logical—ways. Learning to code is not for everyone, but learning a little can go a long way. At least learning the basics of code structure, loops, memory allocation and management, etc. would be my suggestion.

Liquid_Fire 7y ago

> I’m surprised anyone here thinks something like Snaplight would take more than an hour to build I think it would take me longer just to make the icon, having never done anything like that before. Think about all the skills you had previously built up that allowed you to make it in an hour. If someone lacks even one of them, they would never be able to do it so quickly.

giarc 7y ago
Likely just used some stock icons or had previously designed them for another project and never used them.
- tannerc 7y ago
  I’m a full-time designer and designed everything in the app from scratch.
  - sizzle 7y ago
    Hi Tanner, big fan of your design portfolio. As a fellow designer, what inspired/motivated you to make the jump into learning how to code? Was it simply scratching the itch to make higher fidelity prototypes? PS- should designers code? ;)
    - tannerc 7y ago
      Thank you for the kind words! I started coding long, long ago in order to build my web portfolio (back before site builders were a thing). As a result I saw how empowering coding can be. I've always felt being able to code software gives you an ability to solve a lot of your own problems with technology. e.g. I have a lot of private tools I've designed and coded to help me in my day job (such as this simple one I recently open sourced: https://tannerchristensen.com/spf https://tannerchristensen.com/spf). If you're a designer who works on digital products, I think it's only advantageous to know some programming. It gives you empathy for your engineering peers, gives you more insight into how what you design will actually get built (and the constraints/advantages of the technology), and helps you see problems in different—often more linear and logical—ways. Learning to code is not for everyone, but learning a little can go a long way. At least learning the basics of code structure, loops, memory allocation and management, etc. would be my suggestion.