I was given two iPad app review evaluation forms to use when reviewing applications for classroom use. One form, which I will call the evaluation rubric form had six basic domains to evaluate with varying levels that each could be shown within the app. The domains were curriculum connection, authenticity, feedback, differentiation, user friendliness, and student motivation, and each domain had four levels that the application could have adhered to from a scale of 1-4 with 4 being the best.
The second evaluation form I will call the checklist form. This sheet seemed more thorough because it had more "domains," but there were not subsections to each domain, instead there were only yes, or no boxes to check. This sheet had similar domains including curriculum connection, authenticity, feedback, differentiation, user friendliness, student motivation, reporting, sound, instructions, and support page. It also asked questions about cost, blooms taxonomy, and left a space for both a rating and a comment on how you might use this app in your classroom.
After viewing both iPad app evaluation forms I found that I preferred the evaluation rubric to the checklist form because when filling out the checklist I sometimes had a difficult time choosing "yes" or "no," especially when an app fell somewhere in the middle of the two responses by attempting something, but not quite pulling it off. If I was to use either of these sheets in the future I would probably combine the two to create a hybrid form include the basic information that the checklist form had such as app title, cost, creator of the app, content areas, grade, summery of the app, and rating, but I would use the rubric from the evaluation rubric form instead.
The second evaluation form I will call the checklist form. This sheet seemed more thorough because it had more "domains," but there were not subsections to each domain, instead there were only yes, or no boxes to check. This sheet had similar domains including curriculum connection, authenticity, feedback, differentiation, user friendliness, student motivation, reporting, sound, instructions, and support page. It also asked questions about cost, blooms taxonomy, and left a space for both a rating and a comment on how you might use this app in your classroom.
After viewing both iPad app evaluation forms I found that I preferred the evaluation rubric to the checklist form because when filling out the checklist I sometimes had a difficult time choosing "yes" or "no," especially when an app fell somewhere in the middle of the two responses by attempting something, but not quite pulling it off. If I was to use either of these sheets in the future I would probably combine the two to create a hybrid form include the basic information that the checklist form had such as app title, cost, creator of the app, content areas, grade, summery of the app, and rating, but I would use the rubric from the evaluation rubric form instead.