In reply to M0SCU:
Just some thoughts, there is no right or wrong way to display data, just ways that more people like or less people like. Actually displaying the way I like is the right way but you knew that!
So let’s pretend you’re sat in a design meeting like the ones we have where I work and your programming buddies get to rip your work to shreds. You go away bruised and dejected but you come back with something better much better. You also know you get to rip their work to pieces at a later date!
Colour? There is none. Why?
“One hour ago”, no use unless the time now is displayed somewhere. Are you going to continuously update the display so 1 hour ago eventually becomes 2hrs ago? If I’m not updating the display regularly on my device I don’t know how valid 1 hour ago is.
The comments are less useful than the freq/ref and call, use a bigger font etc. to highlight the important stuff. Comments can appear when you select the item. Gives more room for stuff that helps you have a contact with this station.
display the Maidenhead locator and beam heading to spotted station. use the inbuilt GPS to work out beam heading. Much more use than a map displayed on a wee screen.
for stations outside your country display the local time for the station. You’ll know how long he may be there if you know the local time.
6)why not use the RSS feed and have the app get the data from the RSS feed and display the data that way instead of pointing at a web server. OK you’ll need a different app for both 'droid and JobsOS but you get to use the best features of each OS to use rather than trying to make it work just on a browser? I can see the advantage of a browser solution is that the server can grab the summits info and use that rather than the mobile app needing to carry the data it with it.
You may disagree with all the above, that’s fine, this display is for your needs first. Or they may trigger a few “yup, that’s a good idea, onto the todo list with that one.” Or even “he’s mad, forget that!”