11–20 of 70 posts
Have you seen any good examples of iOS apps made from HTML5 with PhoneGap that are actually good?
I'm also a fan of the Travelocity Android app, which was built with PhoneGap.
Does Adobe have a strategy to fight HTML5 or make good progress with open standards b/c of the Typekit purchase? We don't want Adobe to shut down Typekit by any means b/c of how awesome it is and I'm afraid Adobe is resistant to HTML5 as an open standard. Please don't throw money at solutions to killing amazing products which enhance HTML5.
Does Adobe have a strategy to fight HTML5 or make good progress with open standards b/c of the Typekit purchase? We don't want Adobe to shut down Typekit by any means b/c of how awesome it is and I'm afraid Adobe is resistant to HTML5 as an open standard. Please don't throw money at solutions to killing amazing products which enhance HTML5.
I advise the author to review the adobe labs and check out what has been done re:HTML5 and CSS3 over the last year.
http://labs.adobe.com/technologies/edge/ http://labs.adobe.com/technologies/fireworks_css3mobile/ http://labs.adobe.com/technologies/muse/ http://labs.adobe.com/technologies/captivate_html5/
The list goes on.
In addition, they've been a big participant in releasing fonts to typekit already. Why would they close the doors?
Does Adobe have a strategy to fight HTML5 or make good progress with open standards b/c of the Typekit purchase? We don't want Adobe to shut down Typekit by any means b/c of how awesome it is and I'm afraid Adobe is resistant to HTML5 as an open standard. Please don't throw money at solutions to killing amazing products which enhance HTML5.
I watched your two M&A announcements today with keen interest, because I've been watching the overall market change and we're kind of trying to figure out where Adobe fits into things. Where we used to use flash, we're using HTML5 for web and mobile, and where we used to use Adobe SMS, we're now using brightcove, kaltura, and others. We're phonegap hackers as well.
I'm trying to figure out if Adobe is more interested in building supporting tools, or if Adobe is trying to build more of a "one stop" platform a la brightcove appcloud and what people have built out in various verticals for different toolsets (heroku for rails, brightcove for video, pantheon for drupal, etc). As you look forward from the M&A strategy, how do you see the technical solutions coming to market? Are you guys trying to do a rollup, or augmentative strategy? I'm only asking because a lot of recent technical offerings have been out of tune with out Open Source stack approach, and while I'd love to work more with Adobe products, it's been really hard to figure out how and where you guys fit into the new Open Source / Cloud / SAAS / Mobile / HTML5 & CSS3 landscape.
It's obvious you guys are trying to get in front of the trends, but I just can't figure out what that actually is going to look like six months from now.
Any insight there into the overall strategy? I know you might not be able to answer it, but I'd love to know.
Why? Getting past the normal corporate mumbo jumbo, what did you see in the companies that piqued your interest? Was it a talent acquisition? Do you actually see these technologies being integrated with existing adobe technologies (specifically Flash)?
Typekit elegantly solves the licensing, technical, and user experience problems of serving rich typography on the web. That's something we've heard repeatedly is important to our customers, so we're excited to keep growing their business and investigate the right ways to integrate with Adobe applications.
PhoneGap makes it drop dead simple to develop native applications across devices using your existing HTML/JS development skills. As mobile devices continue to fragment and more and more companies need mobile apps deployed across platforms, this problem will only become more important to solve. We're excited to continue to contribute to the PhoneGap open source project, further develop the hosted PhoneGap Build product, and investigate what tool integration may make sense. We've already integrated PhoneGap with Dreamweaver in CS5.5.
So I would say these acquisitions are about talent, technology, and community. They are both amazing teams that have built great products with enthusiastic user bases--and it's important that they stay that way as they grow.
Lots of small companies, like YC co's post demo-day, get bought as talent acquisitions. Adobe doesn't seem to focus on that stage much. Why?
Adobe's DNA seems to be to stuff as many features into a product, even if they're half broken. Does Adobe have a plan to prevent these new products from going the same way?