Closed
Bug 1378997
Opened 7 years ago
Closed 7 years ago
Backend API fetching for Pocket Trending stories
Categories
(Firefox for iOS :: Home screen, enhancement, P1)
Tracking
()
RESOLVED
FIXED
Iteration:
1.27
People
(Reporter: farhan, Assigned: farhan)
References
Details
(Whiteboard: [MobileAS][PocketStories])
Attachments
(1 file)
The API docs for the pocket trending stories can be found on google drive. We will use the "/global-recs" endpoint to display global trending stories Define a struct PocketStory which will have all the values we need to display. The url, title, image_src, domain fields will be required to show a trending story. Use Alamofire to fetch data from the backend API. The results should be cached on disk for at least 3 hours. Different clients will require a different number of Pocket stories. The pocket API lets you specify how many stories to fetch. Make sure the API key is NOT COMMITTED by accident. And for testing only use the development API key. Look at how we store API keys in buddybuild for things like Sentry and Leanplum and try to do something similar for Pocket. And dont forget the tests! The JSON parsing should be tested. You can save a copy of the json returned from the API in the test folder and you can use that to test that the json parsing works correctly.
Updated•7 years ago
|
Whiteboard: [mobileAS] → [MobileCore][PocketStories]
Updated•7 years ago
|
Whiteboard: [MobileCore][PocketStories] → [MobileAS][PocketStories]
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → fpatel
Iteration: --- → 1.26
Priority: -- → P1
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8891041 -
Flags: review?(jdarcangelo)
Assignee | ||
Updated•7 years ago
|
Attachment #8891041 -
Flags: review?(jdarcangelo) → review?(gkeeley)
Attachment #8891041 -
Flags: review?(gkeeley) → review+
Updated•7 years ago
|
Iteration: 1.26 → 1.27
Assignee | ||
Comment 2•7 years ago
|
||
master https://github.com/mozilla-mobile/firefox-ios/commit/24e215fcfff76a23e0a6cf8c4f38250b433d5f3b
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•