Jason, thanks for posting the swikshare link.
My name is Apurva, I am the primary architect of the swik platform. So first off, thanks so much to this community for checking it out.
We are still very much in early beta, and its true that we are taking on a fairly ambitious goal with a small team and limited resources. However, I feel passionate about creating a sandbox to allow designers to explore interaction and content in a very flexible way. So please do keep the feedback coming.
State machines are a natural, visual fit to the user interaction problem. Unfortunately, they are hard to scale and tricky to debug. We have a descent solution to the scale issue with behaviors and the ability to have cross-talk between layers. We have tried to improve debugging/predictability with immediate visual feedback (on what a state looks like) and quick iterations. However, this is an area that will certainly require more work.
I will respond to some of the specific feedback on the individual comments below and am happy to answer additional questions folks have.
The authoring tool is Mac based (10.8 or higher). So please do take it for a spin and let us know what you think. In addition to the HTML5 reader, we have native iOS reader as well. If you would like to use that just let me know and I can post instructions on how to get it. The latter was used to create the La Luna app with an earlier version of the platform (https://itunes.apple.com/us/app/la-luna-the-story-project/id657554982?mt=8).
uh it hurts
Took about 2.7s for me to load. But oddly enough the hero image was the very last thing to load...
The layers are loaded in the order in which they are listed, in other words based on their compositing order.
So one way to deal with the issue you brought up is to have a base layer that indicated loading or progression. For example: http://swikshare.com/#interact/Apuzinio/Loading.
Hope that answers your question.
Thanks for your feedback.
The platform is focused on creating media rich, interactive apps (for example: http://swikshare.com/#interact/Apuzinio/BuildCollage). So at least to some extent, we are focused on what the experience feels like with descent connectivity. http://media.swikshare.com/stuff/SwikSharePreCloudFront.jpg is profiled on a 20 mbps connection. Load time is about 4s, similar to what Julian reported.
I just turned on CloudFront which makes a significant difference to speed and should also help with concurrent users. Total load time drops to under 1.5s. http://media.swikshare.com/stuff/SwikSharePostCloudFront.jpg
I wanted to share an a friends app I have been helping a bit here for the communities feedback. Swik is a tool for creating transitional interfaces. It allows users to create finite state machines in a WYSIWYG editor. I find myself telling people it is like X-Code and Illustrator made a baby.
We are ironing out the interface, but the tool itself is pretty robust. The beta test is free and open for download. Currently, users can export html/css files.
Please try the tool and let us know your feedback. Thanks in advance, looking forward to hearing how all your tests go.
You should clearly state, what Swik does better or different. Also I am missing some kind of demo on the landing page. I had no clue, why I would want to use the app after scrolling through.
Having to dig into the subpages might scare away most of your visitors.
Thanks for your feedback. Yes, we can certainly work on improving our messaging.
What does swik do better? Take a look at this simple interaction which was built in 15 minutes -- built entirely with a visual workflow, no coding: http://swikshare.com/#interact/Apuzinio/FormDupe. You can also download the source to see how its put together. This approach scales to more complex examples as well: http://swikshare.com/#interact/Apuzinio/BuildCollage.
The tutorial is under the Make section: http://swikshare.com/#interact/Whamix/SwikTutorials. That section also has some simple examples that you can use as jumping off points.
Hope this will encourage you to swik away!