Been learning rails, so my friend Timi and I decided to build a simple task manager (Yes, yet another one). We built it custom to how we work. We can add clients and have them login, we can separate tickets from the core of the job and every project has a link to a google docs brief, etc. He started with the base models, I finished up to this. We’re not done, but I’d like feedback on the core, which is the tasks, deliverables, structure and client/ticket management. Thanks. http://ise-demo.helloworld.ng/
Note: If you’re trying to test and getting errors, I’m new to Rails so I couldn’t figure out multi login for one account. So someone else probably logged in while you were in and your token got invalid. So logout then login again to demo it, sorry.
The project description isn’t a link. The project brief is. Usually we agree with the clients about the scope of a project over a shared google document. So that’s what the link is for.
And the Activity list, I feel like it should be ordered according to how near the deadline is. As it is, the task due in 2 days is at the bottom, under tasks that won’t be due for 6.
Yes - another simple task manager
The really interesting thing about creating a task manager is - you learn so many things that will be useful in more ‘serious’ projects - the usual CRUD, validation, notification, constraints, multi-level access, queues, crons, error handling, relationships etc etc etc. So you are very much on point.
My 1/2cent Feedback:
I think it’d be easier on the long run to be responsive for mobile devices. While a mobile app for the major platforms may be in the roadmap somewhere, sometimes, that can be pushed much further down the road than we’d all like.
A textarea might be more useful in place of the input box for adding descriptions (at least under project deliverables).
I spy some Ionic and Foundation in the CSS. I like . Since you have foundation already installed I guess you are half way already there to having a responsive app if you use the Foundation Grid. Unfortunately I could not really play around and give productive feedback becauseI kept getting errors (in the console) whenever i clicked on anything. I will check back again later.
Ionic for font. Stripped foundation for grid. Responsiveness for this is harder cos I didn’t really use Foundation for the layout. It’s just usually a base for stuff I do.
About the errors, I’m new to Rails so I couldn’t figure out multi login for one account. So someone else probably logged in while you were in and your token got invalid. So logout then login again to demo it, sorry.
@FatherMerry If you really want to learn rails, I think you might have too much angular. You app wont feel as zippy as modern javascript apps but you may get to use more of the internals of rails like the rails router, and more of the controllers. As for logging in Devise is the most popular rails gem for that, well documented and thorough. If you want to build an app just on top of rails I think you are on the right track, but rails is a conventional framework (the framework magic happens when you follow the rails convention). There is a rails way to do things and you will skip a decent amount of rails using angular heavily in your app.
I’m learning rails for the api. Basically. Learned a little node before. I’m first a designer, and learning backend is to help me do stuff without being dependent on a developer. I’d rather work API first because it gives me control over UI and interactions. I used Devise for login, but it needs a Redis connection/Some extra stuff I don’t understand (I saw in a random blog post) to be able to log in to the same account from multiple devices. Default Devise invalidates one for the other
. Since you have foundation already installed I guess you are half way already there to having a responsive app if you use the Foundation Grid. Unfortunately I could not really play around and give productive feedback becauseI kept getting errors (in the console) whenever i clicked on anything. I will check back again later.