Coming this spring: Adobe Creative Cloud
This spring will see the release of Adobe’s much-anticipated Creative Cloud service, a new subscription service where you can create, publish, and share your work using Adobe Creative Suite applications, Adobe Touch Apps, and services. We’re excited to announce that a Typekit plan will be included with every Creative Cloud subscription.
What does this mean for you? If you choose to subscribe to Creative Cloud, you’ll receive a Typekit Portfolio plan along with your subscription. You will get all the applications that come with Creative Suite and a Typekit account with access to our full library — all for just $49.99 a month.
If you are an existing Typekit user on the Personal, Portfolio, or Performance plan, you will be able to upgrade to a Creative Cloud subscription. When you do so, you’ll receive a prorated refund for the time remaining on your current Typekit plan. But this upgrade is entirely optional: if you prefer, you can stick with your current Typekit plan just as it is. All of Typekit’s plans will continue to be available as standalone accounts.
As we get closer to the Creative Cloud release, we’ll provide more detail about how you can upgrade. In the meantime, if you have any questions, feel free to ask them here or write support@typekit.com.
11 Responses
Comments are closed.
Intriguing! So, should I infer that a Typekit subscription would work with the other CS products (InDesign, Illustrator)?? Because that would be awesome.
This is just a regular Typekit account — exactly the same as a Portfolio plan today. We are working hard at deeper integrations with other Adobe applications, but you’ll need to wait a bit for news on that.
As an Art Director, I need my work to be faster and lighter, not more bloated. Thank you for keeping TypeKit separate, still.
This is the kind of crap I was worried about when Adobe acquired you. Synergy! Screw that – I just want Typekit to stay exactly as it is.
OK, maybe I’d like you to add one thing: HF&J fonts.
Crap? Bloated? I see it as a first step towards a better integration of webfont services in the design process. In my opinion, that’s a Good Thing (yes, with capitals). Please leave your preconceptions about Adobe at the door!
Says the anonymous poster…
While I’d say ‘crap’ is too vague, bloat it is. For those of you not coding with semantic, balanced code, Typekit integration with Dreamweaver should be a blessing for you. To the rest of us who already know we can integrate Typekit on a local or developer server without need of such cruft, it’s just extra layers of marketing and pomp we don’t need. It serves little purpose save an extra layer of integration that helps those who can’t code with a built in option of selection.
Brady,
As was made clear in the post, Typekit will remain a standalone product. That means you can maintain the same Typekit account you have today. You will not be required to move to Creative Cloud, nor will you be required to use Typekit with any other application.
We have in the past integrated with other services (e.g., About.me, WordPress.com, Behance ProSite), and will continue to do so, while also maintaining the core experience that you’ve come to expect from us. We handcode our sites, too, and no one loves semantic markup more than this team. Rest assured that as we work to make beautiful typography accessible to more people, we also remain committed to users like yourself.
Thank you Mandy, but no need for reassurance. I remember your original post, and my original comment thanking you for keeping Typekit still in standalone. My response was to rogier83R from Adobe mentioning the ‘better integration’. For entry level users, I’m sure it will be.
Ah, I see where you’re coming from now. I do agree with what you say in the context of Dreamweaver. Developers shoud learn to code manually instead of using WYSIWYG editors and whatnot.
I was alluding to the integration of webfonts in *design software*, i.e. Photoshop or Fireworks. I imagine Adobe will be offering cloud software in which webfonts are available for website design/mockups. That would, IMO, be very useful, also for experiencend devs (or, indeed, Art Directors).
There are probably many problems to be solved, both on the technical and the licensing front, but my point is: if it’s ever going to happen, this is the first step.
For the record: I’m not an Adobe employee — ouch! 😉
My apologies for the adobe cheap shot, I should have bit my tongue there:).
If it was built into the core systems, that would be interesting, but I could see it as a hell of an OS-font level conflict. We shall see!
I just recently had an experience where I went to my InDesign font list looking for a font that is on Typekit…but I don’t have on my machine. I had just kind of forgot that I didn’t have immediate access to lovely fonts the moment I thought to use them if I didn’t already own them. It was sort of surreal because it was a complete flip-flop from the old days, when we could use whatever fonts we wanted for print design and were severely limited on the web. My point is, this could be really exciting – I can’t wait to see what the future holds in this area.