Start developing

[Mec-iS]

Resources:

• The data: Articles API
• A mockup of the Android app to take inspiration from
• A collection of graphic resources from our designers (icons, pictograms, fonts, palettes, videoanimations. To access this stuff, request the access to this drive folder)

  Objectives:

• Improve the API about usability/documentation/user experience
• Develop a BackBoneJS app to navigate the data

  Phase One:

• Discuss and design a UI to perform reading and exploring on the data (similar to the Android app?)
• Implement a basic working prototype of a BackBoneJS app

  Phase Two:

• Improve the interaction and graphic experience with dynamic SVG (p5js.org and d3js.org)
• Improve power of semantic data (full text search endpoint, graph exploration, data-visualization)

@Jason-Cooke pushed the initial commit. Let's discuss in here about what we want to realize.

EDITED: Basically user should:

• read the articles' headlines, with possibility to click the url in there, and see the related keywords (25 articles at time/per page)
• search for keyword (with an autocompletion search field?) in different pages
• search for words in the headlines or abstract (only for the 25 visualized articles in the page)
• extra feature: some articles/tweets have children entities (image, video or link), find the way to show these relations

EDITED: The prototype should:

• show 25 articles per page, with their keywords. Let the user click on an article to navigate to the url
• let the user search words in titles and abstracts in the page
• let the user search for keywords (we can implement an endpoint, or a url parameter for that: &keyword=...) in all the articles
• let the user to order by date (using another endopint or parameter as above)

[lerniri]

Also I guess the starting point/prototype is an Android app, but do we have expected functionality defined and written anywhere in the specs ? what we want from the web app and at what phases or is this smth that we are aiming to define in this discussion

[Mec-iS]

@lerniri Access granted (didn't have your GH username before). We can also use the wiki for defining specs. We are developing the Android and the JS-app (and hopefully also the iOS) for the 'xpreader' in parallel. Basically user should:

• read the articles' headlines, with possibility to click the url in there, and see the related keywords (25 articles at time/per page)
• search for keyword (with an autocompletion search field?) in different pages
• search for words in the headlines or abstract (only for the 25 visualized articles in the page)
• extra feature: some articles/tweets have children entities (image, video or link), find the way to show these relations

[Mec-iS]

Articles API endpoint documentation updated: https://github.com/SpaceAppsXploration/rdfendpoints/wiki/Articles-API

[Mec-iS]

User Experience Question: Do we want to push on the fact of the "news" or just give user something interesting to read? The client has to be based on the fact that serves last published information, or act like a sort of archive? I would like to find the good mix between the two.

[claudiopastorini]

We can add on mobile apps push notifications in order to make the client more similar to a news app. Instead with an advaced search we can act like an archive. In this way I think we can find the right compromise

[Mec-iS]

We are planning the development of the API alongside application's features, see SpaceAppsXploration/rdfendpoints#31