Hello friends! I'd like to ask for your opinion regarding multi-line text editing. This suggestion comes from one of our Russian-speaking customers Dolina Zamkova so here is a translated abstract of our email conversation. Current problem: When you write multi-line text, you must press 'Shift-Enter' first, then use 'Enter' to start a new line, then 'Ctrl-Enter' to submit the text. Wouldn't it be easier to have a setting that will allow using Enter to always write multi-line texts, and always submit on 'Ctrl-Enter', like you do it in text messengers? So we could add a new account-wide setting, on the Settings page: () Finish editing by pressing 'Ctrl-Enter' (convenient for multi-line text) What do you think? Do you write multi-line texts in Checkvist at all? Other thoughts of how we could make it better? :)
I think we'll start with a web app that is not clunky :) And then, the hybrid apps for iOS and Android. That's the plan. We're working on current m.checkvist.com usability right now, fixing bugs and performance issues. Quite a lot has been reported already, but chances are we've overlooked something important. So any specific details might help a lot. Thanks!
ReplyDeleteThanks for the quick response. A hybrid app would be fine - users don't care about the backend so much as being served on the front end.
ReplyDeleteAnd yes I've been reading and seeing that the mobile browser is your strategy for now - much to the disappointment of many from what I'm reading in reviews etc. Some have said it's an outright mistake and I tend to agree. Or more like a huge missed opportunity - one that could leave checkvist behind as a viable player. My team here for instance starting using checkvist after much persuading on my part to use a collaborative outliner -only to request that i find another once they starting using the mobile version. I've used outliners all my career and loved finding checkvist for the collaborative ability - but the cross-device limitation is a show stopper for us.
As for specific details - the fact that you have to open a browser and sign-in - And the lack of application buttons and easy access functionality like an app would have. But I think on a deeper level is the feeling of not being in a stable space - not being "served" in that space - it's just an unnatural pattern to go to an app based device and have to find a bookmark and then come to a screen that is dominated by the browser tools primarily - simple as that. An app would also bring in revenue for you and create a stable user base - and be a huge entry port for adoption in general. Is an app really much harder to create than the m. version - in light of all the disadvantages of this approach? Sorry to crash the m. party - but only trying to understand and help here. We know of almost no other successful app that has taken this approach. The m. space is usually reserved for making websites phone friendly - not as a base for task use. What are we missing here?
Hello Jeff,
ReplyDeleteNot so quick a response this time, sorry.
Web applications have certain advantages - no complicated publishing procedures, ability to add fixes as often as needed, easy upgrade. Plus, of course, one code base that runs on the majority of devices. To have a dedicated Android app, iOS app (windows app? blackberry app?) seems a luxury that a team of 2 can hardly allow. Hence the plan to complete the web app functionality and then to create hybrid apps for the major platforms. Thus we'll be able to continue working on one codebase, to publish fixes and features quickly, to have an early access program, etc.
On a lyrical sidenote, back in 2005 people didn't believe you can create a real 'tool' working in browser. 10 years later we're considering a browser OS as quite realistic. And browsers are good for real enterprise level web applications. We're web developers and we do believe that something similar will happen in the mobile app development, even if now it's not so easy to achieve :)
Just a couple of notes regarding m.checkvist.com
- If you 'Add to Homescreen' instead of bookmarking it, it will open not in the browser with browser controls, but as a typical app, and will operate in the same way.
- The feeling of stability doesn't come with native iOS or Android code, unfortunately :) It's simply bugs and more bugs. We're about to publish a new update which, I hope, will fix the majority of this 'shaky-clunky' issues.
The user base and missed opportunities on the market are indeed pain points, that's true. We'll see if we can cover that with hybrid apps.
Hope it explains a bit our stubbornness :)
Thanks - I understand now more where you are coming from and appreciate the process. I am finding the web app sufficient but it's a hard sell with my team. Thanks for all your work on this!
ReplyDelete