You should consider the user impact of doing a single experience across all devices and form factors.
Phones are very tight on real estate so they generally have a drill in paradigm. Get a list, select, pop a view on the stack, pop-out back to the list etc... It's a navigation heavy flow dictated by the real estate.
Tablets have much larger real estate to work with so you should take advantage of that with pop-over views, multiple split panes etc...
The fact that it's HTML5 and not UIKit is irrelevant. Customers want a good experience and expect different experiences on the different form factors.
What I would recommend is to follow a model view controller even in the HTML5 app. Push as much logic as you can down into a common model set of javascript code and differ by the views only. Same as you would do in UIKit ...
If you create a common model and different views based on real estate size, at least you're only building 2 (tablet vs. phone) and not 2 * number of platforms.