Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Pixate promises app UI production in pure CSS

webdev360.com

Post reply on HN
Print view View original

11–20 of 27 posts

Re: Pixate promises app UI production in pure CSS

#11

Post by agscala »

alexobenauer wrote: post #6
JosephRedfern wrote: post #4

$200,000 doesn't seem an awful lot for 3 software engineers and a graphic designer, including premises, utilities and IT.

I'm pretty sure they're currently in YC. I do wonder then what the campaign is for.

It seems like Kickstarter has been used more and more lately as an announcement platform that has the very nice benefit of generating a little extra income on the side.

For now it's going to work because a lot of backers don't actually realize that they have another (probably much larger) source of income to build the product with, and they feel like backing is the only way this product will get off the ground.

Re: Pixate promises app UI production in pure CSS

#12

Post by pcolton »

alexobenauer wrote: post #7
jefflinwood wrote: post #5

This seems like it's going about solving mobile UI problems backwards. I think a better approach would be to fill in the gaps between what a graphic designer is used to (Photoshop, Illustrator, Fireworks), and the UI tools that the different platforms offer - Interface Builder and the XML Layout editor for Android. Interface Builder is definitely visual enough for designers, but most of the "cool" effects for modern…

I agree. CSS Hat currently does this for CSS ( http://csshat.com/ ), but it would truly be great there was a "CSS Hat for native mobile" UI's.

A 'CSS Hat for native mobile UI's" is basically what Pixate supports. That is, we can take CSS, and style native iOS (and Android) components just like you can web components. Pixate is the engine that enables all of this (whereas in a web page, the browser is doing all the rendering for you).

Re: Pixate promises app UI production in pure CSS

#13

Post by RandallBrown »

jefflinwood wrote: post #5

This seems like it's going about solving mobile UI problems backwards. I think a better approach would be to fill in the gaps between what a graphic designer is used to (Photoshop, Illustrator, Fireworks), and the UI tools that the different platforms offer - Interface Builder and the XML Layout editor for Android. Interface Builder is definitely visual enough for designers, but most of the "cool" effects for modern…

Check out Expression Blend.

Yeah, it's for Windows apps, but it's still pretty sweet. The designers at my old company could basically use it instead of photoshop and turned out some pretty impressive stuff.

http://www.microsoft.com/expression/products/Blend_Overview....

Re: Pixate promises app UI production in pure CSS

#14

Post by alexobenauer »

pcolton wrote: post #12
alexobenauer wrote: post #7

Earlier quoted context omitted.

I agree. CSS Hat currently does this for CSS ( http://csshat.com/ ), but it would truly be great there was a "CSS Hat for native mobile" UI's.

A 'CSS Hat for native mobile UI's" is basically what Pixate supports. That is, we can take CSS, and style native iOS (and Android) components just like you can web components. Pixate is the engine that enables all of this (whereas in a web page, the browser is doing all the rendering for you).

I think I like the CSS Hat model better because it generates the code that I then have complete control over. First, that can be helpful when learning the language. Second, it's really nice because of its tweakability. If the CSS Hat dev's decided to implement a stroke as a border, but I know it would look better as a layered drop shadow, then I can make that adjustment. If there are any other quirks or bugs, I can fix them with the resultant code. With the pixate model, I can't do that, as far as I understand (please correct me if I'm wrong!!).

Re: Pixate promises app UI production in pure CSS

#17

Post by pcolton »

alexobenauer wrote: post #14
pcolton wrote: post #12

Earlier quoted context omitted.

A 'CSS Hat for native mobile UI's" is basically what Pixate supports. That is, we can take CSS, and style native iOS (and Android) components just like you can web components. Pixate is the engine that enables all of this (whereas in a web page, the browser is doing all the rendering for you).

I think I like the CSS Hat model better because it generates the code that I then have complete control over. First, that can be helpful when learning the language. Second, it's really nice because of its tweakability. If the CSS Hat dev's decided to implement a stroke as a border, but I know it would look better as a layered drop shadow, then I can make that adjustment. If there are any other quirks or bugs, I can f…

You can edit the CSS with Pixate in the exact same way. It doesn't get 'compiled away', the runtime optimizations happen behind the scenes. The CSS can remain in your project as a resource, much in the same way you reference your CSS in an HTML page.

Re: Pixate promises app UI production in pure CSS

#19

Post by bgramer »

pcolton wrote: post #15

Appcelerator (creators of Titanium) supports Pixate by becoming first corporate sponsor. http://developer.appcelerator.com/blog/2012/08/join-us-in-su...

I've been watching this with keen interest since it was first announced here sometime ago. Unfortunately, at the pace Pixate is raising funds on Kickstarter, it doesn't look like they'll achieve their goal. Does this mean they're screwed, or will they still push this product out the door through their corporate sponsor Appcelerator?

Re: Pixate promises app UI production in pure CSS

#20

Post by pcolton »

bgramer wrote: post #19
pcolton wrote: post #15

Appcelerator (creators of Titanium) supports Pixate by becoming first corporate sponsor. http://developer.appcelerator.com/blog/2012/08/join-us-in-su...

I've been watching this with keen interest since it was first announced here sometime ago. Unfortunately, at the pace Pixate is raising funds on Kickstarter, it doesn't look like they'll achieve their goal. Does this mean they're screwed, or will they still push this product out the door through their corporate sponsor Appcelerator?

Have you made a pledge? ;-)
Post reply on HN