Adobe just announced an updated suite for the Creative Cloud subscribers with enhanced applications and added functionality. Those with creative cloud subscription will automatically get the updates along with the ability to keep older versions or simply replace them.
A lot of the designers and developers were moving away from Adobe Fireworks and Photoshop in recent years due to Adobe not giving us updates for Fireworks and it’s vast ability to do something that UX designers and designers in general loved; Pages! Yes each page could be a standalone page and have the ability to share assets from other pages.
With Fireworks getting stuck in 32-bit java code world, we all started looking to alternatives, Bohemian Coding created Sketch from the ground up as a 64-bit application for OS X and brought in features from Fireworks in a different way in the form of Artboards.
We’ve used artboards before in Illustrator but Artboards in Sketch gave you a totally new way of constructing application design, may it be mobile, web or desktop.
Sketch also gave us pages and the ability to create symbols and other neat features, besides it being a completely vector driven design workflow.
For at least 3 years we as designers have been using Fireworks and switching over to Sketch. Adobe saw a lot of designers leaving their tools and decided to do what they knew would keep the designers (who hadn’t switched yet)
Adobe finally brought Artboards to Photoshop CC 2015 and they’ve done it very close to how Sketch treats artboards. Popular prototyping application InvisionApp is already supporting Photoshop Artboards and with it expanding it’s user base yet again.
I still have to experiment with Photoshop and see how it plays with creating multi-size exports like Sketch does. But the plug-in support alone still gives Sketch the upper hand, but those familiar with Photoshop will certainly love this new feature of Artboards lifted from Illustrator and given new meaning.
After using Adobe’s Fireworks (Initially Macromedia Fireworks) for over 15 years to design websites, mobile apps, logos, envelopes, and everything under the sun. I’ve decided to switch over the Sketch 3 (I know it seems like I waited on Sketch 2, it’s cause I didn’t know Sketch existed.)
Used Adobe Fireworks entirely to design some remarkable apps for both iPhone and iPads (including retina) and faced at least 10 crashes a day (mainly because Fireworks is still a 32-bit application running on top of Java 6); and Adobe decided to kill all efforts to update it like they’ve continued to advance the versions of Photoshop and Illustrator (both good tools as you’ll read in the article below)
Meng To does an excellent job in comparing the applications available in the market.
Fireworks.. still not vector
A comparison between Adobe Fireworks, Sketch and Photoshop, and why Sketch is the perfect tool for user interface design.
We’ve all been reading rumors about Retina displays for Mac since December 2011, and with the arrival of the new iPad with a retina display, the updates to the current OS X (Lion to include @2x icons) hardware specs aiming for graphics with very high resolution capabilities. It’s no wonder why the rumors make sense. WWDC 2012’s icon displaying the tons of screens representing iPhones, iPod Touch and iPads is another hint.
From a developers point of view and looking at the resolutions of iPhone 4/4S and iPad (3rd gen) we’re some trouble designing for retina iPad with a resolution of 2048×1536 which is higher than any display smaller than a 30″ apple cinema display to show the entire view of the retina iPad. We’ve having to design for a 1024×768 resolution on our MacBook Pro 17″ or a hi-res MacBook Pro 15″ (with 1680×1050, which barely fits the iPad in portrait mode) plenty of scrolling to see the screen, infact designing for iPhone 4/4S’s retina display with 960×640 resolution we’re cramped a little in portrait mode.
When laying out the storyboard in Xcode we’re presented with a 1x design/layout of the iPad and as you add screens and views the display again feels cramped and you have to keep zooming out and then back in and eventually we start using the sidebar for the storyboard.
The iPhone is also displayed in 1x when laying out the storyboard and as you add more screens you start scrolling a lot (which is much easier when using a mouse or touchpad thanks to the gestures)
A retina display mac would rightly be in place as it’ll let the user display the entirity of the iPad or iPhone display as we’re testing the app we’re building in the iPhone Simulator and wouldn’t have to switch between retina and regular.
As rumored a 15″ MacBook Pro would have a retina resolution of 2880 (reg. 1440) x 1800 (reg. 900) which would easily fit a retina display of a retina iPad (2048×1536) in landscape but not so much in protrait thats where the higher res (1680×1050) 3360×2100 would be perfect to display a portrait retina iPad and portrait retina iPhone along with the ability to layout storyboards with out a lot of scrolling.
And if they continue the tradition with a 17″ MBP with 3820*2400 would make it a blast to design clean UI for the retina displays.
So I’m looking forward to these new MacBooks with sick retina displays and beefy graphics from nVidia.
Update: I just noticed in the iOS Simulator that I can use the scale-down feature when simulating using the retina display modes by up to 50%. They did think of everything 🙂
With all the explosion on Mobile Web and Applications. Theres’ several offerings that let you create mobile web. Some great things to keep in mind is how your application will look like in the several mobile browsers that are out there, such as Mobile Safari (iPhone, iPad, iPod Touch), Mobile Firefox (Android and others), Mobile Opera (Several platforms).
37 Signals goes into details on how to watch out for these issues and the solution of-course.
Well after reading articles and dugg stories of the iPhone Pwnage Tool first being in existance, then being delayed from released, then being completely closed-out and shutdown and sold to a private company to finally being released on April 3rd, 2008. I was in complete awe and amazement. So I did what everyone who is an early adaptor and downloaded the tool, loaded it up on my MacBook Pro as quickly as I could. I ran into one issue which caused me a little delay (my home Mac was the primary sync point for my iPhone). If I were to use the tool on the iPhone from my MBP it’d erase my music/videos and this would cause me to listen to nothing on my way back home.
This is where AFPd came in handy, I created a private WiFi network, connected to the iPhone and copied over all of my music to this iTunes Library into a new playlist (which will now sync to the iPhone). Once that was done I “erase and sync”ed the iTunes with the iPhone. Now I was ready to Pwn my iPhone. I was then missing the ipsw files required by the Pwnage tool, which I was easily able to download thanks to ‘iphone.unlock.no’.
I then put my phone into recovery-mode and was able to use the iPwner tool to flash the rom (using the downloaded 1.1.4 ipsw)
Then I created a new custom 1.1.4 ipsw using the Pwnage tool & the original 1.1.4 ipsw.
Once the iPhone was pwned, I restored it using the new custom ipsw that I just created using iTunes (option + restore button, select file)