Value Judgements in Interface Design @meshu09
With Ryan Singer of 37signals
- MESH 2009 WOOHOO!!!by Andre at 4/6/2009 1:06:57 PM
by MDM at 4/6/2009 1:10:28 PM- Standing room onlyby MDM at 4/6/2009 1:10:37 PM
- Talking about the shift from being a web design firm to a product firmby Andre at 4/6/2009 1:11:18 PM
- Ryan has worked at 37Signals for 6 years. They use to build sites for clients then they decided to build an app for them self. Basecamp was born.by MDM at 4/6/2009 1:11:29 PM
- They are now a software company.by MDM at 4/6/2009 1:11:49 PM
- How does the work day look at 37Signals...Is the topic for today.by MDM at 4/6/2009 1:12:35 PM
- Doing a bit of a demo of some internal 37Signals apps in devby Andre at 4/6/2009 1:13:48 PM
- Interface design is 90% copywritingby Andre at 4/6/2009 1:16:12 PM
- Everyone at 37Signals runs a local copy of their apps and can iteratively make changes to help them communicate with the rest of the team.by Andre at 4/6/2009 1:17:08 PM
- Its very common to make (develop) collections of lists like to-dos, email, tweets etc. It helps to see how the changes you make to these lists in real time so you can see the new style and how it effects where those list appear in your app.by MDM at 4/6/2009 1:21:16 PM
- Main theme of the demo/workshop is iteration. Once you have your core foundation, the 37Signals team seems to work best working inside the code as they make changes. In real life this is no different than a designer/front-end dev using tools like Firebug, etc. to improve and streamline your UI in near "real-time".by Andre at 4/6/2009 1:23:58 PM
- Traditional UI Workflow - - Wireframes - PSD's - HTML - Actual Codeby MDM at 4/6/2009 1:25:26 PM
- Suggesting that design task should include wireframing + PSDS + HTML/CSS... should not be broken up into multiple disciplines.by Andre at 4/6/2009 1:26:46 PM
- When design + developers can work tightly together you end up with a better product... cannot just have programers in control of the software. You need tight collaboration.by Andre at 4/6/2009 1:27:58 PM
- Designers should be responsible for everything the customer sees.by Andre at 4/6/2009 1:29:00 PM
- Can't successfully use a product without the UI... software is all about the experience.by Andre at 4/6/2009 1:29:40 PM
- Having designers who can work inside version control tools and be comfortable in the code/templates is an ideal state.by Andre at 4/6/2009 1:31:07 PM
- The loop involved with a designer is real long compared to the action of "reload" when a coder makes a change.by MDM at 4/6/2009 1:31:13 PM
- @enricobianco New saying: "If its not code, its wishful thinking." #meshu09by maplealmond via twitter at 4/6/2009 1:32:13 PM
- Ryan is pimping MVC (Model, View, Controller) right now... designers play in the views (templates)by Andre at 4/6/2009 1:32:46 PM
- So the user experience is important, but this is still _software_ we're building. That makes a _lot_ of sense. #meshu09by enricobianco via twitter at 4/6/2009 1:33:40 PM
- Web apps have three layers View - 90% HTML, Controller - Moves data between model and views, Model - Meat of code. (DB, logic)by MDM at 4/6/2009 1:36:58 PM
- by rccgd via twitter at 4/6/2009 1:37:28 PM
- Web pages have only two layers CSS and HTML.by MDM at 4/6/2009 1:37:38 PM
- 37Signals work flow. Programmers are in control of Controllers, Helpers, Models. Designers on have access to Views.by MDM at 4/6/2009 1:39:52 PM
- More on MVC over on Wikipedia - tinyurl.comby Andre at 4/6/2009 1:40:03 PM
- MVC frameworks allow devs and designers to work simultaneously instead of some concrete workflow/process. #meshuby verneho via twitter at 4/6/2009 1:40:53 PM
- One of the main differences between Templates and View is that the data that changes in removedby MDM at 4/6/2009 1:43:21 PM
- It feels like Ryan is saying "Designers aren't smart enough to touch that programmer code." As a programmer, that feels weird. #meshu09by maplealmond via twitter at 4/6/2009 1:43:50 PM
- When they start a project they discuss and try to explain the Model in plain english. This helps the designers understand what the model is and how they have to design. Gets everyone speaking the same language in a simple way.by Andre at 4/6/2009 1:44:56 PM
by MDM at 4/6/2009 1:49:29 PM- So in other words, you can't have "single specialty" people on your team. Designers need to be able to understand dev. Devs need to be able to talk to clients, designers, etc. Collaboration is key.by Andre at 4/6/2009 1:50:36 PM
- Suggestion just made to break out your code/CSS into really simple pieces. Keep all your CSS for your comments in a comments.css file. Allows you to jump back in and understand really easily a year later when you need to make an update.by Andre at 4/6/2009 1:53:35 PM
- Customers, designers, developers, EVERYONE should be using the same language to describe how the code works. Same words for same stuff for everyone. Makes support and long term understanding easy.by Andre at 4/6/2009 1:54:29 PM
- Domain Driven Language. domaindrivendesign.orgby MDM at 4/6/2009 1:54:57 PM
- Keep your templates as HTML as possible in order to allow designers to retain control.by Andre at 4/6/2009 1:54:59 PM
- Simple HTML with simple inline bits of code/data... no heavy processing in the templates.by Andre at 4/6/2009 1:55:38 PM
- #meshu09 But... but... but what if I WANT the table columns generated dynamically by an enumeration of the attributes?by maplealmond via twitter at 4/6/2009 1:55:40 PM
- Gotta be careful of developers who want to get more clever and add code.by Andre at 4/6/2009 1:56:06 PM
- If you don't need to complicate things, don't do it. Only automate stuff once it's a pain in the butt for a long time and you know exactly what should be automated and how...by Andre at 4/6/2009 1:56:49 PM
- Lets Review. Designers are res. for specific layers of software code. Designer and Programmers work together on source code.by MDM at 4/6/2009 1:57:58 PM
- Lets Review How: Programmers are your best friend. Get the coders to set up the apps locally and check out code via version control. Create naming conventions that make sense.by MDM at 4/6/2009 1:59:25 PM
- Questionsby MDM at 4/6/2009 2:01:00 PM
- Talking about how for example if you are approached with a new feature that is "important" and needs to be on a specific page. Someone comes and says this feature need to be there. You push back and say where. Everything can't be important. If they are nothing is.by MDM at 4/6/2009 2:08:31 PM
- Ryan giving amazing explanations on feature overload and how to do with it #meshu09... Communication being the key. Also tradeoffs + %'sby timothyleung via twitter at 4/6/2009 2:09:03 PM
- Ryan's Digits
@rjs on Twitter
rjs.tumblr.comby MDM at 4/6/2009 2:11:24 PM - When to use Ajax? If you need to produce a whole new list you should just reload.by MDM at 4/6/2009 2:15:43 PM
- Thats it folks.by MDM at 4/6/2009 2:15:56 PM
- Design seminar at MeshU Ryan Singer, UI Designer/Product Manager 37signals.by MDM at 4/6/2009 1:13:14 PM
- Who's Blogging
-
Andre
MDM
- Crossposting
-
This liveblog is being crossposted to MDM.
- Translate
- Options
-
Comments
Turn viewer comments off and on.
Turn comments off
- Share
