Tim Fletcher

Tim Fletcher

Co-founder at FotoJournal Joined over 6 years ago

  • 0 stories
  • 3 comments
  • 7 upvotes
  • Posted to First paying customer: a very short parable about my first attempt at building a SAAS product., in reply to Nathan Manousos , May 23, 2014

    It absolutely is possible, even advisable, to ask someone to pay for a product before it exists. How else do you know whether the pain you've identified — and are planning to build a business on — is sufficient that someone will pay for it?

    Off the top of my head, Zapier, WP Engine and Close.io all received payment from customers before their product existed. Granify's co-founder managed to persuade customer to pay him 15k to build a product that didn't exist because the customer wanted it so badly. If there's a business there people will pay in advance.

    It's so easy for developers and designers to build a product that nobody uses. Trivially easy. It's incredibly hard to build a SaaS business that makes enough to live off.

    0 points
  • Posted to Gridlover—establish a typographic system with modular scale and vertical rhythm, Apr 10, 2014

    To what extent to designers rigidly stick to a vertical rhythm? I looked at a few sites that are known for their typography (e.g. Medium) and they don't adhere as many articles suggest you should.

    I've tended to simple make sure I have a healthy leading for my line widths and plenty of whitespace so the text can 'breath'. Sticking to a grid is great for learning the basics but seems to not be used by many professional designers.

    0 points
  • Posted to Bourbon Neat—A lightweight semantic grid framework for Sass and Bourbon, Mar 26, 2014

    Thoughbot are doing some great work on both of these projects. There's some key differences between Bourbon/Neat and Compass though.

    Firstly, Bourbon/Neat do not require any 'unsemantic' classes in your markup (if you have an issue with that). No row and column classes required.

    Secondly, Bourbon/Neat are pure Sass whereas Compass has some native C extensions. That's cool because you can use libsass (via grunt-sass), the super-fast C implementation of Sass rather than the Ruby based one. If you're using large frameworks like Foundation then compilation can become quite slow. libsass helps with this a lot.

    2 points
Load more comments