Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Search the Community

Showing results for tags 'invision'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Categories

  • Management
  • Design
  • Requirements
  • Development
  • Test
  • Atlassian

Categories

  • Personal
  • Professional
    • Management
    • Requirements
    • Design
    • Development
    • Testing
    • Operations
  • Interesting
    • Atlassian
    • Security
    • E-Commerce

Categories

  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Operations
  • Atlassian
  • Security
  • E-commerce

Categories

  • Management
  • Design
  • Requirements
  • Development
  • Testing
  • Operations
  • Atlassian
  • Security
  • E-Commerce
  • Others

Categories

  • Thoughts
  • Debate
  • Health
  • Hobbies

Categories

  • Personligt
    • Åsikter
    • Humor
    • Spel
    • Träning
  • Allmänt
    • Internet
    • Program & tjänster
  • Intressant
    • Prylar
  • Professionellt
    • Management
    • Krav
    • Designs
    • Webbutveckling
    • Test
    • Atlassian
    • säkerhet
    • Förvaltning
    • Ehandel
    • Wordpress
  • Personligt_

Categories

  • Prologue
    • About This Book
  • The Tools
    • Jira Software
    • Confluence
    • Jira Service Management
  • The Inception Phase
    • Portfolio Management
    • Project Management
  • The Design Phase
    • Design as part of the Inception phase
    • Design as part of the Requirement phase
    • Working with design libraries
  • The Requirement Phase
    • Definition of Requirements
    • The four levels of Requirements
  • The Development Phase
    • Atomic design
    • Estimations
  • The Test Phase
    • The Definition of Test
    • Types of Test
  • The Operations Phase
    • Release Management
  • The Post Go-Live Phase
    • Incidents
    • Changes
  • Notes
    • My Muses
    • Research

Categories

  • Theme Building
  • Javascript Framework
  • CSS Framework
  • IPS: Pages
    • Database Templates
    • Block Plugin Templates
    • Page Templates
  • Custom Applications
  • Tips & Tricks

Categories

  • Europe
    • Central Europe
    • Eastern Europe
    • Northern Europe
    • Southeastern Europe
    • Southern Europe
    • Western Europe
  • North America
    • United States of America
    • Canada
    • Mexico
    • Caribbean
    • Central America
  • South America
    • Argentina
    • Bolivia
    • Brazil
    • Chile
    • Colombia
    • Ecuador
    • Falkland Islands
    • Guyana
    • Paraguay
    • Peru
    • Suriname
    • Uruguay
    • Venezuela
  • Africa
    • Northern Africa
    • Central Africa
    • Western Africa
    • Eastern Africa
    • Southern Africa
  • Asia
    • Central Asia
    • East Asia
    • South-Eastern Asia
    • Southern Asia
    • Western Asia
  • Oceania
    • Australia
    • Fiji
    • Kiribati
    • Marshall Islands
    • Micronesia
    • Nauru
    • New Zealand
    • Palau
    • Papua New Guinea
    • Samoa
    • Solomon Islands
    • Tonga
    • Tuvalu
    • Vanuatu

Categories

  • Shared Hosting
  • Virtual Private Server
  • Cloud Hosting
  • Dedicated Hosting
  • Co-Location
  • Hosting Services

Categories

  • Professional
    • Management
    • Design
    • Requirements
    • Development
    • Testing
    • Operations
  • Interesting
    • Atlassian
    • Security
    • E-commerce

Categories

  • Defects
  • Ideas
  • Development
  • ☑ Archive

Categories

  • Professional
  • Management
    • Agile
  • Requirements
  • Design
  • Development
    • Frontend
    • Backend
  • Testing
  • Operations
    • Hosting
  • Atlassian
  • Security
  • E-commerce
    • CRO
    • SEO
  • Interesting

Categories

  • Professional
    • Management
    • Requirements
    • Design
    • Development
    • Testing
    • Operations
  • Interesting
    • Atlassian
    • Security
    • E-commerce

Forums

  • General
    • Open Forum
    • Support
  • Professional
    • Management
    • Requirements
    • Design
    • Development
    • Test / QA
    • Operations
  • Interesting
    • Atlassian
    • Security
    • E-commerce
    • Invision Community
  • Jobs
    • Looking for employee / consultant
    • Looking for Job / Assignment
  • Building The Site's Forums
  • Destiny 2's Discussions
  • The Journey's Discussions
  • Cinephilia's Topics
  • Diablo 4's Diablo 4 Topics
  • Shadownessence's Topics
  • sensory hyperreactivity's Topics
  • Wolcen's Wolcen Topics
  • Quality Assurance Heroes's QA Topics
  • Visual Studio Code's Forum
  • Adobe Illustrator's Adobe Illustrator Forum
  • Sketch Guru's's Sketch Topics
  • Requirements & test management in Jira's Topics
  • Microsoft Teams's Microsoft Teams Discussions
  • Figma's Figma Topics
  • Microsoft Planner's Microsoft Planner Topics
  • Psychology's Psychology Topics
  • Microsoft Word's Microsoft Word Topics
  • Microsoft Powerpoint's Microsoft Powerpoint Topics
  • WordPress Devs's Wordpress Topics
  • Ornamental Design's Ornamental Design Topics
  • Adobe Photoshop's Photoshop Discussions
  • Agile 2's Agile 2 Topics
  • Agile 2's Agile 2 Principles
  • Microsoft Outlook's Outlook Topics
  • My Book's Discussions
  • Outriders's Outriders Discussions

Categories

  • Jimi's Files
    • Curriculum vitae
    • Presentations
    • Certificates
  • Management
  • Requirements
  • Design
    • Fonts
  • Code
  • Test
  • Operations
  • Atlassian
    • Certificates of Excellence
  • Security
  • Ecommerce
  • Invision Power Services
    • JWSE Support Tickets
    • JWSE Task Management
  • Shadownessence's Files
  • WordPress Devs's Wordpress Files

Calendars

  • Project: JWSE Workboard
  • Project: JWSE Workboard
  • Community Calendar
  • Professional Events
  • Management Events
  • Requirement Events
  • Design Events
  • Development Events
  • Test Events
  • Atlassian Events
  • Operations Events
  • E-commerce Events
  • Destiny 2's Events
  • The Journey's Events
  • Cinephilia's premieres
  • Diablo 4's Diablo 4 Events
  • Agile 2's Agile 2 Events

Blogs

  • How to start your own blog
  • Sketch Blog
  • Building The Site's Blog
  • Destiny 2's Destiny 2 ramblings
  • The Journey's Stories
  • Diablo 4's Diablo 4 blog
  • Sketch Guru's's Sketch News
  • Requirements & test management in Jira's News
  • Agile 2's Agile 2 Blog

Categories

  • Personal
    • Humor
    • Music
  • Professional
    • Management
    • Requirements
    • Design
    • Development
    • Testing
    • Operations
  • Interesting
    • Atlassian
    • Security
    • E-commerce
  • Destiny 2's Videos
  • The Journey's Videos
  • Cinephilia's Trailers
  • Diablo 4's Diablo 4 Videos
  • Wolcen's Wolcen Videos
  • Visual Studio Code's Videos
  • Adobe Illustrator's Adobe Illustrator Videos
  • Sketch Guru's's Sketch Videos
  • Requirements & test management in Jira's Videos
  • Microsoft Teams's Microsoft Teams Videos
  • Figma's Figma Videos
  • Microsoft Planner's Microsoft Planner Videos
  • Psychology's Psychology Videos
  • Microsoft Word's Microsoft Word Videos
  • Microsoft Powerpoint's Microsoft Powerpoint Videos
  • WordPress Devs's Wordpress Videos
  • Ornamental Design's Ornamental Design Videos
  • Adobe Photoshop's Photoshop Videos
  • Agile 2's Agile 2 Videos
  • Microsoft Outlook's Outlook Videos
  • Outriders's Outriders Videos

Categories

  • Movies
    • Action Movies
    • Adventure Movies
    • Animated Movies
    • Comedy Movies
    • Crime Movies
    • Drama Movies
    • Fantasy Movies
    • Horror Movies
    • Romance Movies
    • Sci-Fi Movies
    • Thriller Movies
    • Western Movies
  • TV Shows
    • Action TV Shows
    • Adventure TV Shows
    • Animated TV Shows
    • Comedy TV Shows
    • Crime TV Shows
    • Drama TV Shows
    • Fantasy TV Shows
    • Horror TV Shows
    • Romance TV Shows
    • Sci-Fi TV Shows
    • Thriller TV Shows
    • Western TV Shows

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me

Found 7 results

  1. Figma has been in the news for designers for a while and it is in many ways praised as the one tool that will save us all. I am still skeptical because to me Figma is a generalist tool, and I am used to working with specialist tools. I will go over the selling points that Figma have listed as to why people make the switch from Sketch to Figma. On the Figma website they list 3 main selling points for making the switch: Less is more, Faster in the cloud and Better Teamwork. The collaboration aspect has been their biggest selling point so far as far as I am concerned, but let us go over them one by one and see how they appeal to certain groups. I will look at these selling points from two points of view. The Isolated design team, which would be where most design studios and larger companies with dedicated design teams would fit. The included design team which is where the team is working alongside the requirements and development team members. Less is more I could not agree more. Having to juggle multiple tools at once is a bad experience for everyone. The design tool is just one tool and it must connect to the overall flow of the build phases. That means that the design should be connected to the code and the requirements. As far as I know there is no design tool that have that today, so we still need to have that as separate tools. Abstract for release management When it comes to both requirements and development, which are the two adjacent disciplines to design, then version management is very important. Abstract is by far the best tool right now for maintaining a controlled version management, which also can follow the same flow as the code. This allows for locking a design, while also continue working on it in a controlled way. While Figma have a version history built in, it is just that. Version management of single assets with no connection outside the design flow. It is not what is needed for collaboration outside the design discipline, even if it is nice to see who did what when. InVision for prototyping I do not do a lot of prototyping and usually the built-in functions in Sketch works fine to illustrate a flow. If I need to do a full prototype I would either use InVision or Axure depending on the situation. Are the functions in Figma as advanced as InVision or Axure? I don't think so, but then again I have not seen any reason to dig into it too much. I doubt it is something that will make or break a decision for a designer. Zeplin / Avocode for design handover While design handovers are less common when working with proper pattern libraries, a lot of people still do not have that workflow in their organization. Having tools like Zeplin or Avocode to allow developers to match colors, fonts, margins and paddings becomes important in that case. For the isolated design teams this is a lifesaver as it reduce the need to communicate with the build team. For the included teams it is simply an additional feature, like a nice-to-have. This is because the included teams will of course collaborate directly with the rest of the team, which makes static information less important. Overall it is not bad that Figma have the basic tools for prototyping and design handover, quite the opposite. The missing part for me is that they do not have the features to replace Abstract and the features for prototyping and design handover are not exceeding the features of the specialized tools. I would argue that Figma would best fit small, isolated teams that need a generalist tool over specialized ones or due to cost. Faster in the cloud One selling point for Figma is that it works everywhere. This is good news if you are forced to work in an organization that only allow PC computers or if you prefer to work on a Linux for whatever reason. Personally I fail to see the importance of this because you should choose the tools that make you most efficient. If you are limited because the organization prioritize hardware over people, then leave right away. Never work for companies that don't care about its people. The only reason why this is good for Figma is because they want to bring everyone into Figma and as such it must be available on all systems. It does not make the design process more efficient and collaboration of multiple disciplines inside a design tool is far from problem free. I would say this is only needed if you have the design handover in the design tool or if your workflow is based on passive collaboration. Better Teamwork This is Figma's biggest selling point in my opinion and it is one they promote a lot. Collaboration is an interesting thing though and it clearly means different things to different people. Figma define collaboration as getting passive feedback through comments and the ability to work on the same designs together. Comments are passive collaboration The ability to add comments is the very lowest form of collaboration. It is a passive form of communication and while it is nice to not having to email people to get a comment on a design suggestion, it is best suited for isolated teams that do not have access to the people that they need to communicate with. For included teams this might at best be something you use when you are not working or to get feedback from people that are not part of the build stream that you are working in. Included teams would get far better results directly communicating with developers and stakeholders than asking for comments. Adding Notes to your design While it is sometimes useful to add notes in the design, for example during a workshop, I do not see this as a big selling point as I could just as easily get something like Sketch Notebook to do the same thing. So while we all want better collaboration, I fail to see how passive communication with external sources will be helpful in most situations. Unless you are an isolated team with little to no access to the people you need to collaborate with. Figma has the same type of collaboration like many other tools that also cater to the same working conditions where you work apart from the people you need to collaborate with. Is this something that is crucial for a modern designer today? In some cases it might be, but for people who work in an agile and included way this would never be an important feature. It should also be noted that Sketch are also adding these type of features in a near future and if they are similar, then this would not be a big selling point in the future. Design System (not listed as a selling point) Figma also promote their design system as an important feature, but not as a reason why people move from Sketch to Figma. I bring it up because design systems are used a bit carelessly these days and sometimes seem to be interchangeable with pattern libraries. In both Sketch and Figma a design system is just design asset management. It is not connected to code in any way, other than that certain values can be seen using the inspect tools in Figma. You would need something like Invision DSM to actually connect code to assets, but usually you will still have a manual step between design and code. Should you make the switch? This is the big question, just like it was some years ago when Sketch challenged Adobe. Back then it depended on your workflow and your finances mostly, but also what UI you preferred. To some it was also about small company vs big company or just to have the latest hot tool on the market. Here are some the reasons I see. Figma is the latest hot tool There is no denying this fact ever since WordPress announced they would go for Figma as the official tool back in 2018. It is now the talk of the town and many are looking at Figma to replace Sketch. If you are one of those that follow the crowd, then Figma is probably pretty attractive right now for this reason alone. Many designers still work in isolation Sadly this is still true, even if designers are slowly moving into the build teams. When you are cut off from the daily interactions of the build teams, then you have no choice but to work with passive communication. Having that inside your design tool is a good option if you are crippled when it comes to good communication. Sketch will get similar features so this may not be the selling point it once was. One cheaper general tool Money always define the tools we use and the possibility to reduce cost by using one general tool rather that several specialist tools is not a bad thing. If you rarely use the full features on the specialist tools, or if you are struggling with the cost for multiple tools, then Figma is not a bad alternative. It probably has most of the feature you use every day already built in. Everyone can use Figma This is something that should not be underestimated. Many companies suffer from low trust and as such managers have the need to control the work even if they should not. In such situations it is very nice to have a tool that is accessible everywhere and the commenting function is also a big bonus. The only drawbacks with Figma as I see it, is that it is an isolated design tool and it is not an offline tool. It has no connection to the build flow and it really needs Abstract as a plugin or a similar product that also have design release flows. The fact that it require Internet also put some limits on where I can or can not work. There are of course plugins to both Figma and Sketch that require Internet connection as well, so the limitations are not only in Figma. My conclusion when it comes to Figma is that for me there is nothing that make me want to make the switch. The tools are roughly the same and when I need it I will bring in another tool to supplement for example prototyping. It does not fit into my workflow of direct communication where design follows the same cadence as development and test. At least not for the moment. For isolated design teams, or smaller design teams that do not need additional features I would say this is a great fit due to it's acessibility, indirect collaboration features and price. For included design teams I would still suggest Sketch + Abstract as the most efficient and collaborative way of working.
  2. Figma has been in the news for designers for a while and it is in many ways praised as the one tool that will save us all. I am still skeptical because to me Figma is a generalist tool, and I am used to working with specialist tools. I will go over the selling points that Figma have listed as to why people make the switch from Sketch to Figma. On the Figma website they list 3 main selling points for making the switch: Less is more, Faster in the cloud and Better Teamwork. The collaboration aspect has been their biggest selling point so far as far as I am concerned, but let us go over them one by one and see how they appeal to certain groups. I will look at these selling points from two points of view. The Isolated design team, which would be where most design studios and larger companies with dedicated design teams would fit. The included design team which is where the team is working alongside the requirements and development team members. Less is more I could not agree more. Having to juggle multiple tools at once is a bad experience for everyone. The design tool is just one tool and it must connect to the overall flow of the build phases. That means that the design should be connected to the code and the requirements. As far as I know there is no design tool that have that today, so we still need to have that as separate tools. Abstract for release management When it comes to both requirements and development, which are the two adjacent disciplines to design, then version management is very important. Abstract is by far the best tool right now for maintaining a controlled version management, which also can follow the same flow as the code. This allows for locking a design, while also continue working on it in a controlled way. While Figma have a version history built in, it is just that. Version management of single assets with no connection outside the design flow. It is not what is needed for collaboration outside the design discipline, even if it is nice to see who did what when. InVision for prototyping I do not do a lot of prototyping and usually the built-in functions in Sketch works fine to illustrate a flow. If I need to do a full prototype I would either use InVision or Axure depending on the situation. Are the functions in Figma as advanced as InVision or Axure? I don't think so, but then again I have not seen any reason to dig into it too much. I doubt it is something that will make or break a decision for a designer. Zeplin / Avocode for design handover While design handovers are less common when working with proper pattern libraries, a lot of people still do not have that workflow in their organization. Having tools like Zeplin or Avocode to allow developers to match colors, fonts, margins and paddings becomes important in that case. For the isolated design teams this is a lifesaver as it reduce the need to communicate with the build team. For the included teams it is simply an additional feature, like a nice-to-have. This is because the included teams will of course collaborate directly with the rest of the team, which makes static information less important. Overall it is not bad that Figma have the basic tools for prototyping and design handover, quite the opposite. The missing part for me is that they do not have the features to replace Abstract and the features for prototyping and design handover are not exceeding the features of the specialized tools. I would argue that Figma would best fit small, isolated teams that need a generalist tool over specialized ones or due to cost. Faster in the cloud One selling point for Figma is that it works everywhere. This is good news if you are forced to work in an organization that only allow PC computers or if you prefer to work on a Linux for whatever reason. Personally I fail to see the importance of this because you should choose the tools that make you most efficient. If you are limited because the organization prioritize hardware over people, then leave right away. Never work for companies that don't care about its people. The only reason why this is good for Figma is because they want to bring everyone into Figma and as such it must be available on all systems. It does not make the design process more efficient and collaboration of multiple disciplines inside a design tool is far from problem free. I would say this is only needed if you have the design handover in the design tool or if your workflow is based on passive collaboration. Better Teamwork This is Figma's biggest selling point in my opinion and it is one they promote a lot. Collaboration is an interesting thing though and it clearly means different things to different people. Figma define collaboration as getting passive feedback through comments and the ability to work on the same designs together. Comments are passive collaboration The ability to add comments is the very lowest form of collaboration. It is a passive form of communication and while it is nice to not having to email people to get a comment on a design suggestion, it is best suited for isolated teams that do not have access to the people that they need to communicate with. For included teams this might at best be something you use when you are not working or to get feedback from people that are not part of the build stream that you are working in. Included teams would get far better results directly communicating with developers and stakeholders than asking for comments. Adding Notes to your design While it is sometimes useful to add notes in the design, for example during a workshop, I do not see this as a big selling point as I could just as easily get something like Sketch Notebook to do the same thing. So while we all want better collaboration, I fail to see how passive communication with external sources will be helpful in most situations. Unless you are an isolated team with little to no access to the people you need to collaborate with. Figma has the same type of collaboration like many other tools that also cater to the same working conditions where you work apart from the people you need to collaborate with. Is this something that is crucial for a modern designer today? In some cases it might be, but for people who work in an agile and included way this would never be an important feature. It should also be noted that Sketch are also adding these type of features in a near future and if they are similar, then this would not be a big selling point in the future. Design System (not listed as a selling point) Figma also promote their design system as an important feature, but not as a reason why people move from Sketch to Figma. I bring it up because design systems are used a bit carelessly these days and sometimes seem to be interchangeable with pattern libraries. In both Sketch and Figma a design system is just design asset management. It is not connected to code in any way, other than that certain values can be seen using the inspect tools in Figma. You would need something like Invision DSM to actually connect code to assets, but usually you will still have a manual step between design and code. Should you make the switch? This is the big question, just like it was some years ago when Sketch challenged Adobe. Back then it depended on your workflow and your finances mostly, but also what UI you preferred. To some it was also about small company vs big company or just to have the latest hot tool on the market. Here are some the reasons I see. Figma is the latest hot tool There is no denying this fact ever since WordPress announced they would go for Figma as the official tool back in 2018. It is now the talk of the town and many are looking at Figma to replace Sketch. If you are one of those that follow the crowd, then Figma is probably pretty attractive right now for this reason alone. Many designers still work in isolation Sadly this is still true, even if designers are slowly moving into the build teams. When you are cut off from the daily interactions of the build teams, then you have no choice but to work with passive communication. Having that inside your design tool is a good option if you are crippled when it comes to good communication. Sketch will get similar features so this may not be the selling point it once was. One cheaper general tool Money always define the tools we use and the possibility to reduce cost by using one general tool rather that several specialist tools is not a bad thing. If you rarely use the full features on the specialist tools, or if you are struggling with the cost for multiple tools, then Figma is not a bad alternative. It probably has most of the feature you use every day already built in. Everyone can use Figma This is something that should not be underestimated. Many companies suffer from low trust and as such managers have the need to control the work even if they should not. In such situations it is very nice to have a tool that is accessible everywhere and the commenting function is also a big bonus. The only drawbacks with Figma as I see it, is that it is an isolated design tool and it is not an offline tool. It has no connection to the build flow and it really needs Abstract as a plugin or a similar product that also have design release flows. The fact that it require Internet also put some limits on where I can or can not work. There are of course plugins to both Figma and Sketch that require Internet connection as well, so the limitations are not only in Figma. My conclusion when it comes to Figma is that for me there is nothing that make me want to make the switch. The tools are roughly the same and when I need it I will bring in another tool to supplement for example prototyping. It does not fit into my workflow of direct communication where design follows the same cadence as development and test. At least not for the moment. For isolated design teams, or smaller design teams that do not need additional features I would say this is a great fit due to it's acessibility, indirect collaboration features and price. For included design teams I would still suggest Sketch + Abstract as the most efficient and collaborative way of working. View full blog article
  3. Every digital business faces a crucial challenge when they begin to scale—how to ship better products, faster, while still creating consistent user experience on every screen. It’s incredibly hard to do. To solve for this, the world’s most successful digital product companies leverage the power of comprehensive design systems to scale consistently. It’s how they collect and connect interdependent UX components—including colors, symbols, fonts, shapes, and more—guided by clear design standards.
  4. I stepped in to support my colleagues with the UI design for the new website. My assignment was to take the graphic profile already put in place and build new pages in Sketch where needed.
  5. InVision har länge varit ett självklart val för att skapa snabba prototyper för många. Senaste tiden har det varit lite osäkert vart InVision passar in med allt fler som kikar på Abobes XD som börjar bli intressant. Så kommer då Invision Studio och allt blir spännande igen! [embed width=960" height="540] [/embed] Det är svårt att inte bli exalterad utav detta. Invision Studio träffar rätt på så många punkter att det nästa är lite läskigt. För mig som jobbar en del med kod så är det svarta interfacet gudomligt mycket skönare än Sketch bleka interface. Craft’s intuitiva gemensamma bibliotek inbyggt och dess Git liknande pull/push system känns supertrevligt. Rapid prototyping i samma stil som både deras nuvaranda lösning och Adobe XD’s smidiga interface känns klockrent. Animeringar direct i designen känns helrätt och möjligheten att samarbeta i designen är gudomligt. Freehand och InVision kommentarer verkar vara inbyggda direkt i systemet och jag ser en Zeplin liknande inspect funktion också! Nu fattas bara att man direkt integrerar Webstorm med koppling direkt till assets så har vi ett fullfjädrat pattern library. Det vore en dröm att jobba med så design och kod kan leva direkt tillsammans. Inte realistiskt är kanske, men man kan väl få drömma? Invision Studio kommer i januari 2018 och jag har självklart redan signat upp mig för det så fort Invision Studio blir tillgängligt. Du kan signa upp du också på Invision Studio’s hemsida. Vad tror du om Invision Studio och tror du det kan utmana Sketch och Adobe?
  6. [embed] [/embed] För designers som mig själv så är detta fantastiska nyheter i Photoshop med asset management och art boards, men den största behållningen i den här presentationen är utan tvekan Project Comet som i ett enda svep slår ihop det bästa från Sketch3 och InVision som jag skrev om igår. Nyheter i Photoshop 2015.1 När det gäller Photoshop så är det en hel del godsaker som den nya startskärmen som ger dig en bra översikt över saker som recent file thumbnails, document presets, Libraries access, och personalized tutorial content. Detta kan så klart ställas in i inställningarna så du får det du vill ha. Det mest intressanta för mig är dock Artboards. Nu kan jag äntligen samla designs i ett dokument istället för att ha dussintals i olika mappar för varje möjlig upplösning och variant. Funktionaliteten är utmärkt och lätt att jobba med. Creative Cloud Libraries har fått ett lyft också och nu är det superenkelt att dra in alla delar av ett dokument på en gång istället för att dra in dem en och en. Vektorstöd har förbättrats avsevärt och du kan nu dra in vektorgrafik och hantera inne i Photoshop och genom att dubbelklicka vektorfilen så kommer du direkt in i Illustrator så du kan göra justeringar. Förutom detta så kom det en hel del andra saker också och du kan hitta det mesta som är nytt i 2015.1 här: http://blogs.adobe.com/richardcurtis/2015/12/11/photoshop-new-features/ Sketch3 / InVision utmanaren Comet Sedan har vi då vår Sketch3/InVision klon med kodnamnet Comet. Detta ser utan tvekan ut att bli den mest intressanta Adobe produkten för 2016 för mig (Ok, Muse nya funktioner är rätt intressanta också) då den verkar kunna ge Sketch3 och Invision en rejäl fajt, speciellt som Sketch endast finns för Mac idag. Med liknande funktioner som Sketch3 och med några riktigt vassa funktioner som repeat grids och visuell koppling mellan skärmar i prototypläget så känns Comet som superintressant och jag ser fram emot att testa Comet i början på 2016!
  7. Att byta från Photoshop till Sketch 3 är ingen liten omställning när man som jag suttit i Photoshop i lite drygt 15 år, men precis som allting annat just nu så är allting nytt och spännande och Sketch 3 är ett riktigt, riktigt bra program som växer för varje dag som går. Att jag är pigg på att prova nya saker är nog ingen nyhet för de flesta och just nu så är nästan allting jag gör professionellt helt nytt och spännande. Allt från verktyg till arbetsmetodik och samarbetsformer är nytt och ytterst formbart, vilket är helt underbart! Ett av de nya sakerna jag jobbar med är just Sketch 3 som används flitigt av vårt systerbolag Fjord som jag samarbetar mycket med nu. Det som Sketch gör bra är att det är väldigt fokuserat på just webb och med sina enkla, men ändå kraftfulla funktioner. Till skillnad från Photoshop som är en gigantisk verktygslåda så är Sketch mer renodlad och jag måste erkänna att det känns som man tagit det bästa från Photoshop, Illustrator och till och med InDesign. Ytterligare ett plus är att Sketch 3 passar fantastiskt bra tillsammans med InVision så det blir ett sömlöst flöde mellan design och prototyping. Faktum är att jag börjar se att just Sketch 3 och InVision börjar bli något av en industri standard och jag har så klart också börjat kika på hur jag kan använda detta flöde i framtiden, både privat och professionellt. Sketch 3 kostar klart överkomliga $99, finns bara till Mac (precis som att du skulle jobba med något annat som hipster designer?!) och saknar exportfunktion till annat än PDF och sina egna format. Förutom det ser jag bara positiva saker för Sketch 3, så jag ska kika på lite tutorials och börja lära mig alla snabbkommandon och funktioner nu när jag har lite ledigt. Har du provat Sketch 3 och i så fall, hur gillar du det i jämförelse med andra grafiska verktyg du använt?
×
×
  • Create New...