For EA and other entertainment companies, it's probably not about finding cheap money or growing headcount for its own sake. Cheap money funds more "art." They can try to create new games or movies or tv series and gamble that one or more becomes a hit or even a franchise that makes a return on that cheap investment. Maybe a return that covers the cost of multiple failed attempts. Similar to VCs.
Somnium Guitars [0] also makes guitars with easily hot swappable pickups. They have a mounting system where you can put most pickups into their mounting module and click it into place from the back of the body. It’s still a bit pricey, but starts at a less expensive $2,495 MSRP vs $4,500 from Relish.
Away is a modern lifestyle brand creating thoughtful products designed to transform travel.
Since our launch in February 2016, we have become one of the fastest growing consumer brands in the world. We have sold millions of travel products, grown from a team of four to over 250, expanded shipping to nearly 40 countries, opened seven stores across two countries, and launched several new products and experiences that are inspiring more people to travel the world. And we know that’s just the beginning!
They're £58.33 plus £10.00 shipping which converts to roughly $100 US. I'm not that frugal, but Jesus this shirt better be tip top quality and last longer than 6 months for $100.
The names are used in Japan. Some of these names (e.g., "Strike Gold") conjure up an old-school Americana. This is intentional. Japanese denim brands (who now make these shirts as well) are very reverent of pre-1960s Levis.
They use the English names in Japan. If you google for the Japanese official websites for these brands or even their products on rakuten.co.jp you'll see the brand names in English.
I took a look at a few of the go rest frameworks and settled on https://github.com/emicklei/go-restful. It seems like it's the most feature complete and mature of the pack. I'm playing around with a go-restful and gorp (orm-ish library in go) combination at the moment.
I found this project (https://github.com/jmcvetta/lgtts) that has managed to integrate go-restul/gorp and is also setup so it can be deployed to heroku.
For #1, the zip code 42223 spans Christian KY and Montgomery TN. The zip code 97635 spans Lake OR and Modoc CA. 95961 can be the city of Arboga, Olivehurst, or Plumas Lake.
The mapping isn't unique. I think the best you can do is restrict your pulldown to the possible choices. Even then, sometimes there are small cities and towns that you don't expect.
Combining first/last name into a name field and auto-detecting card type were easy wins for the shopper, but in user testing, we found that detecting city/state from a zip code had some potential issues.
First, the format of the form without city/state surprised some users. One user said something like "where do I put my city and state?" They ended up appending it to the street name. Then they filled in the zip code and saw that it fetched the city/state and then realized how it worked then went back to delete it from the street name field.
Also, in the U.S., some zip codes can return multiple cities and states. Our solution was to populate a pull down of the possible values for both fields.
It turns out there are small towns/cities that we didn't return from a zip lookup, so city had to be editable for these users. We added a "Let me type it in" option on the bottom of the city pulldown for those users, who are hopefully the minority.
For Australia we have the user enter a postcode which then allows them to pick a suburb from a drop down. We have some text next to the postcode field to explain this.
I really like your checkout process. It's very pretty and unobtrusive. One note: your dropdown fields don't update when I have focus and type in a value until after I've left the field (unlike the native control which updates as I type) which makes keyboard-only navigation a bit tricky.
Perhaps having the user enter their location information in the order country, zip, city, state, street would provide a better experience. It's not what they would be used to, but it's at least consistant (information is entered from less precise to more precise).
Having to build an additional "let me type it in" option seems like it increases the complexity and confusion. One of the banks I use asks for the zip first and then populates the city and state text fields on the lines below. This also has the benefit of working if Javascript is disabled.
What do you do if there are multiple options for the city/state? What if your city happens to not be one of the options you provide? That's why we needed to add an option for the user to fill it in.
In that case the user can type it in themselves. The textfields are fully editable after all. I would expect that it is faster for user to type in the correct city if you get it wrong than for them to have to move their mouse to the keyboard and select it from a drop down list, and if it isn't in the drop down then this method is faster.
I'm surprised how well AngularJS has worked for us.
Currently, we're using it for the shopping checkout page and also for the merchant dashboard. The dashboard is all driven by AngularJS (using $resource/$http api calls). The checkout page is more like Twitter, in that we preload data in the DOM when it's rendered, but there are API calls via AngularJS to create the order, check quantity, etc. These pages are actually served directly from our CDN.
As far as how it's worked for us. We've actually rewritten our dashboard and checkout page twice, and it look some getting used to on how to structure our controllers. Getting used to writing directives instead of using jQuery and doing DOM manipulation in our controllers also takes some discipline, because it's just way simpler to drop some selectors and event bindings/triggers in your controller.
The way AngularJS encourages you to keep any dom manipulation out of the controller and to think about reusable directives has really helped for readability and maintainability of the code base. We're consistently surprised how quickly we can implement features because of AngularJS. We've actually said, "Wow, that was easier than I was expecting" quite a few times.
However, there are some hurdles. $http doesn't support file uploads, the stable release doesn't support custom http headers with $resource, only one ngView, etc. That said, I still would not hesitate to recommend AngularJS.
Did the limitation of having only one ng-view affect your project at all? I'm embarking on a new project using Angular and there are mixed opinions on the web. People that were shouting against it have come back saying that it's actually not so bad [1].
In the first iteration, we thought multiple ngViews would have been useful, but it didn't prevent us from achieving the design we wanted. You can use ngInclude to accomplish a similar effect, if you don't need the routing.
AngularUI seems to have a solution for nested views/routing here (https://github.com/angular-ui/ui-router). Although, I would think about your routes and the pieces of your web application and rethink whether you really need ngView. Using ngIncludes for pieces you want to reuse might make more sense.
It sure makes more sense, but you need to write boilerplate code to map URL state to ng-include changes/updates. It would be nice if it was out of the box.
I don't know the details of your app but maybe you should consider using ngView in the outer most container, then everything inside the container can pick the appropriate template via ngInclude. That's the path we took in our first iteration, this current iteration actually doesn't need nested/multiple ngViews.
ng-view is not simply a view (I think the name confuses most users), if you want multiple ng-views you will probably need more routers. Maybe there are some use cases for it, I just can't really think of one. You will pretty much split your application in N.
You really really really really want to keep those kind of things in directives.
Anyway, I read about it sometime ago on a github issue it is 'planned'.
Totally agree with Jack on this, I enjoy working with AngularJS. I think the learning curve could be made less steep with better docs. It would be great if they were moved to GitHub to make contributing easier.
