June 2017 Overview Update

New open source, simplified, and powerful interface programming language for cross-functional teams

To ask questions join our Slack community at slack.viewsdx.com and ask any questions tagging @tom in the questions channel. Follow us on Twitter for spontaneous 👻 updates or contribute to Views language on GitHub.

1. Big shout out to Darío Javier Cravero
2. 02:28 Continuous Design in cross-functional teams
3. 08:18 Design as you build, showcase
4. 22:05 You must have this download sample app
5. 23:50 Installation
6. 27:07 Compose views with blocks
   Containers: Horizontal, Vertical, List, Custom
   Content: Text, Image, SVG, Capture
7. Rules
   34:00 - Each View must have top level container
   35:10 - Use regular CSS properties in camelCase instead of dashes
   36:35 - Any extra (more than one) empty lines you put between blocks the higher container they move to, we call it Proximity Nesting
   49:40 - Parts can be imported by name from other .view file
   55:00 - Data can be imported through props from other .data file
   56:30 - Tests can be created for every functionality scenario and imported via props from .tests file
8. 57:55 We’ve done lots of experiments
9. 58:40 We’ve got a strategic partner and a core product in production with 50 daily million users
10. 59:35 We are growing the team
11. 01:01:01 Next challenges, animations, error handling, native interactions
12. 01:05:10 What tools would you need?

Mentioned links:

Craft from InVision Labs, Zeplin, iTerm, Views Syntax Highlighters

🤦‍ Mistakes I’ve gracefully committed along the way:

01:06 “Benefits that benefit” bollocks 🥇
07:45 “That is a begzszist” should say “basis”
10:26 “…with… The quality you end up with” hmmm…
13:50 “Two views is a fork”, clearly I was hungry🍴
21:06 HTML, CSS, JS is only considered hardcore by non-developers 👀
22:50 “Source -file-, public -file-, build -file-” I meant “-folder-”
01:05:48 “It’s a react DOM” should say “It’s an HTML DOM”