Where the design community meets.
Co-Founder at zero.london Joined almost 9 years ago
This is great! Thank you David
Basically it's a kit to enable Adobe employees to translate their ideas to an MVP and bring a product to life.
The original kit comes in a red box and includes a pre-paid card with $1000 (they can spend this as they wish), a pre-paid Starbucks card, a notebook to write down 'bad ideas' and a manual with 6 core parts to help understand how the process works. This is for people from all backgrounds.
You can get from the site all the resources you need to 'generate innovation' - I guess you won't get the $1k though :)
Hope this make sense.
Design, Product, Tech, Lego and Geeky stuff in general. Enjoy :)
First half of the year, I'm going to:
TheNextWeb - http://thenextweb.com/conference/europe/
UX London - http://2015.uxlondon.com
Definitely worth a look if you work on Apps and web stuff!
Thank you James,
This is extremely useful! I would assume that a 360x640px resolution would be a good start in order to support small screen devices and you would increase the size in proportion moving to hdpi, xhdpi, etc.. So we don't have to design for specific devices for Android? Like most popular Galaxy or Nexus screen sizes?
If this is correct, what would happen if I want to take advantages of a bigger screen dimension? (Talking just about mobile and not table at the moment)
Thanks a lot! Giovanni
Fantastic! This is a great start Alex! Thank you.
I spent some time exploring the Google Material resources over the last few weeks (impressed with it from the release). The video resources are fantastic, same as the community.
Just a more technical question, on iOS - mobile - you design for basically 3 screen sizes (iPhone 4/5, 6 and 6Plus), with Android, supporting multiple screen sizes, what would it be the standard size to design components for?
Thanks a lot!
Thanks again Malte!
you have two buttons, one to 'add to collection', and one to 'add to basket' - you're worried users won't understand the difference - you're worried that users will think '+' also adds something to a basket?
This is exactly it! :)
Have a look at this if you get chance, to get a better understanding of the scenario: https://dribbble.com/shots/1896006-Shopa-Product-Tile?list=users&offset=2
An user see the 'add' feature just when on hover (clicking on the tile and going to the product page when from mobile). The space is tiny and probably so far the '+' would be the best solution to go with, assuming the you wouldn't add anything into the basket from a product tile, if you don't see further details on the product (including size and other related variations).
Thanks a lot Malte for sharing your opinion.
It's a tricky one also because I need to create consistency across platforms and screen sizes (from big desktops - where would be ok go with a verbal CTA - to small screens or native apps - where the flaxibility is much less).
The basket icon is yes solid for an 'Add to Basket' action, but the confusion would come when you don't have just the '+' on a tile that is referring to 'Add to Collection' rather than 'Add to Basket'.
Probably would be easier if I try to represent the 'collect' action and not the 'add to' action. But again, not easy, as most of the platforms out there are using the 'add to' behaviour applied to different scenarios and just few (so far on Fancy) have both 'Add to Basket' and 'Add to something'.
If you have more thoughts please feel free to share.
Maybe it's just an impression, but I don't see the bacon here...
Giovanni hasn't upvoted anything yet.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.
We just launch https://spaceboard.tech
It's a little experiment to create a simple global job board to help talents looking for their next role in tech and companies looking to connect with candidates, as well as to play with Next.js.
The idea was to make a streamlined and stress free experience, to provide only the key informations needed to scan the content easily, and free for both talents and companies to use.
We shared a little bit of the technical learnings here (for those interested in the technical side of things): https://medium.com/zerostories/5-tips-for-building-a-next-js-app-576fd1f7c065
Any comments/feedback would be appreciated.