Home / survey / Addressing 31 suggestions and feedback from Kwik Survey – Part 1

Addressing 31 suggestions and feedback from Kwik Survey – Part 1

You may have seen the results already of our Kwik Survey (if not, they are here: http://t.co/ZeQ7JUw). The pages does not show the list of suggestions and feedback receive. Below, the list with our comments. Again, thanks for your participation!

1) “Generally it’s a great and very useful product for people with little to no coding experience. What makes it shine is the really good customer and technical support and the frequent updates. As for feedback and suggestions if i’ll encounter any while I’m working in Kwik I’ll let you know, like I did so far.”

Well, no comments here besides, thanks!

2) “Need Kwik for Fireworks”

Not in the plans for this moment (sorry!). Kwik is still in its infancy and there is lot to do for the Photoshop version. Maybe in the future…

3) “Dear developers. I bought your tool 30 min after watched your video. I’m looking for your grow in such a nice idea/software like this. Watch Adobe Flash Catalyst, or take it files to Lua. Integrate with CoronaUI is the way to go. Skinning!”

Thanks for buying! Some CoronaUI will come in a near future (mostly the ones related to interactive books). Skinning? You can skin everything as you are in Photoshop 🙂

4) “Great communication with developer via e-mail, this is key for a new product at this early stage of development.”

Thanks!

5) “Option to link in developer written lua modules inside Kwik would be good and then attach modules to objects. Eg you could write some player controls and then import that lua modull as a Smart Object or something then attach it to a layer or Kwik object then when you export you have hooked in your controls already. Saving lots of time and provide a way for Kwik developers to share extension modules with other Kwik non developers and better themselves.”

Note taking. Not in near future plans thou as Kwik targeted audience are illustrators and designers, and this type of feature is very developer oriented.

6) “I need three different things: – moving objects along a polyline – timelines (when I can start one animation immediately after another one) – main thing: please divide the produced LUA code on two parts: computer-generated part and user-edited part. See “SpriteDeck” to understand how to do this.”

Path animation (we are going call it with this name) is coming in a near release. Timelines in Photoshop are not planned for anytime soon (very complex to implement). Kwik differs to SpriteDeck, which mostly work on screen positioning. As Kwik builds the entire code (not in a template format) according the unique interactions our users create, makes no sense to create templates at this time. Also, our users (mostly novices) like to learn more about Lua, reading the generated files.

7) “Very pleased with Kwik. Would love path animation.”

Check answer above. Coming soon.

8) “BRILLIANT!!”

Loved this one!

9) “I do not use your product, I have an few clients I consult that are professional publishers, that I recommended your tool to. I still like getting updates to pass info about your tool to 3rd party clients wishing to program there own apps (publications) to mobile platforms, that do not have the experience my company does in programing with out such tools.”

Thanks for your support!

10) “So far I really like your product. As before, I’m planning to purchase. I’ve just been spending time getting better at Photoshop since that’s my “weak spot” in the workflow! So just been doing a lot of Photoshop tutorials so I’m not completely lost while using that application.”

Take your time. We will be here.

11) “Timers, message alert, stay awake when screen locks.”

Timers will debut soon. Message alert just entered in the feature list. Stay awake when screen locks must be solved by Corona (currently their SDK does not allow this).

12) “I use it in my classroom. I think the comic creation would be a great tool for Art teachers, especially! The eBook could be used for all classes — student-made textbooks, etc.”

Thanks for supporting us!

13) “Love it! I do need help integrating Particle Candy.”

We are planning to add external integration (especially after the survey results). Coming after v1.5, which will be a big update.

14) “Great Product!!!! I am a Very Happy User!! You have anticipated my concerns with the questions above. This tells me you are looking into functions that I would see helpful. Animation, Animation, Animation!”

Animation was clearly a winner. Next builds will bring a few more tricks. Some of them: path animation, loops and widgets (pre-done code like pulse, bounce, etc).

15) “Could be a good idea if Kwik allow draggable elements that interact with other elements/buttons, to create match figures etc.”

Still in design planning. We didn’t have yet any great idea on how to implement this (ok, the drag part is easy but, what happens when you drop?). Coming in the future.

16) “Still feels half baked, but it’s a good early effort!”

Yes, this is a cookie nobody wants to wait to cook perfectly. After 45 days, we have brought dozens of new features, all of them suggested by our users. Can you imagine what we will do in 4.5 months or 4.5 years? J

Tomorrow we publish the last 15 ones!

 

2 comments

  • You wrote:
    5) “Option to link in developer written lua modules inside Kwik would be good and then attach modules to objects. Eg you could write some player controls and then import that lua modull as a Smart Object or something then attach it to a layer or Kwik object then when you export you have hooked in your controls already. Saving lots of time and provide a way for Kwik developers to share extension modules with other Kwik non developers and better themselves.”

    Note taking. Not in near future plans thou as Kwik targeted audience are illustrators and designers, and this type of feature is very developer oriented.
    >>>>>>>

    Contrary to your thinking, I think that adding the ability for developers to build modules is extremely friendly to designers– so that they don’t have to! It could be the most designer-friendly thing you do. Let the community build widgets, templates, code modules (like folks who build template libraries for Balsamiq mockup tool), and your user base will soar. Widgets baby!

    • Bill, fair enough. My point here was, there are so many features that are requested now by users that, this particular one is not in the top of the list (to create an external module for 3rd party development). I am working with the Spriteloq team on some kind of integration. Hope to do the same later with the Particle Candy team. Do you have other ideas?

Leave a Reply

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Strictly Necessary

these coolies are for WP-SpamShield, gdpr-wp, woocommerce, paypal

PHPSESSID, SJECT16, JCS_INENREF, JCS_INENTIM, gdpr, woocommerce_cart_hash, woocommerce_items_in_cart, woocommerce_recently_viewed, wordpress_, wordpress_logged_in_, wordpress_sec_, wordpress_test_cookie, wp_woocommerce_session_, AKDC, akavpau_ppsd

Functionality

WordPress cookie created when auto-saving a post in the editor.

wp-saving-post, wp-settings-, wp-settings-time-

Performance

google analytic

__utma,__utmb,__utmc,__utmz,_ga,_gid,_gat

Advertising