Archives for future

Crossing the Chasm with Mobile Apps

Reading my emails this morning, I was surprised with a particular one coming from Moglue, a long time competitor of Kwik. After three years promoting and selling their DYI (do it yourself) storybook tool, they just announced they are closing the business due lack of continued funding (according CrunchBase, Moglue has received a total of $990K in the period of 2 years). Although  the announcement is really surprising (I wish Kwiksher had the almost $1M in investment as well), there are a few indications happening in the market at this moment that may explain some of their reasons. Just to make things clear, my words below are just assumptions as…

What can you expect about Kwik “Next”?

As promised, I would like to give you an update on the planning/designing/developing phases of Kwik “Next” (there is not final name yet for Kwik’s major update, coming in the last quarter of this year). Before anything else, I am assuming you read my last posting about Kwik and Corona and know already that Kwik “Next” will still be available for Corona SDK only. What are the major goals for Kwik “Next”? I have set 3 main goals for the next major release. They are: Phase 1) Code Infrastructure: Some of you probably noticed that large projects may stuck when pages have more than 200 layers/variables (a limitation from Lua). Some…

What is in the future for Kwiksher?

Now that everybody knows the news (in case you were disconnected last week, take a look at our big announcement), I think it is important to clarify some topics and provide a glimpse of the things in our pipe for the future months. First of all, I would like to reinforce my happiness in having both David and Carlos on board. More than good friends, they share the same vision I have for the future. Their arrival also means Kwiksher is in the right path to fulfill my goal in providing tools to creative people, enabling them to bring their stories to life. In sum, it is a recognition that together, you, the user, and…

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


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

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


google analytic