I think the general point is that for certain apps, a native environment is better suited to allow easy access and organization mentally. For a to-do list, it makes some sense. That way you can ⌘+TAB over to it, add or check your to-dos, then go back to whatever it is you were doing without worrying about browser tabs.
Another benefit is that you don't have to worry about cross-browser compatibility. If it looks good in your app on your dev computer, it should look the same on everyone else's.
I do agree that since it's written using web tech, they should have a web accessible version as well. Maybe they do, and I didn't see it?
Regardless, I think the end product is more important then HOW they made it or what language was used. If it works great and looks great, who really cares?
Comments
I think the general point is that for certain apps, a native environment is better suited to allow easy access and organization mentally. For a to-do list, it makes some sense. That way you can ⌘+TAB over to it, add or check your to-dos, then go back to whatever it is you were doing without worrying about browser tabs.
Another benefit is that you don't have to worry about cross-browser compatibility. If it looks good in your app on your dev computer, it should look the same on everyone else's.
I do agree that since it's written using web tech, they should have a web accessible version as well. Maybe they do, and I didn't see it?
Regardless, I think the end product is more important then HOW they made it or what language was used. If it works great and looks great, who really cares?