+ Add Question

On what technologies is Todoist built?

A different question today... on what technologies does todoist web run? Do you use any frameworks (front- backend) or is everything coded from ground up besides jquery?

All responses

David Trey staff
Replied on Dec 15, 2013 - 20:16 UTC

Hello Michel,

On the front we use a lot of JavaScript (our own code, no libraries) and on the back mostly Python.


Best regards,
David

G
Gileno
Replied on Aug 11, 2014 - 12:39 UTC

Hello David, which technology you use to create desktop apps (windows / mac)?

David Trey staff
Replied on Aug 11, 2014 - 12:44 UTC

Gileno,

On Windows .NET Framework + Chromium. Not sure what's the equivalent of the standard framework on the Mac, but there we also use Webkit inside the frame.


Regards,
David

G
Gileno
Replied on Aug 11, 2014 - 12:47 UTC

I was thinking it had something with html / css, very cool.

Thanks.

David Trey staff
Replied on Aug 11, 2014 - 12:50 UTC

Gileno,

Yes, all our desktop apps and plugins are basically frames build on the platform's standard framework with a browser engine inside that connects to Todoist.com

Given that our web-app has a dynamic design, is based on HTML5 and can work offline, it's much easier for us to maintain all these plugins so every change we make on the web will automatically apply to all plugins, with minor exceptions (handling of emails as tasks, which is usually the plugin's unique feature).


Regards,
David

Deepu Mohan Puthrote premium
Replied on Dec 11, 2014 - 10:51 UTC

Using the browser engine directly on the app is insane. I guess it gives you much more flexibility and freedom. However this seems to be a tougher path to go along. Have you hit any bottle necks in this approach?

David Trey staff
Replied on Dec 11, 2014 - 12:52 UTC

Hello Deepu,

So far not. Given that in its core, Todoist is built as a web-app, it works great in a browser engine. We've also made it offline compatible and given how fast modern browsers perform, there's basically no performance impact compared to a native app :-)


Regards,
David