Project 3 - Tweeter
Tweeter is a basic twitter app to read and compose tweets from the Twitter API.
Time spent: 23 hours spent in total
The following required functionality is completed:
- User can sign in using OAuth login flow.
- User can view last 20 tweets from their home timeline.
- The current signed in user will be persisted across restarts.
- In the home timeline, user can view tweet with the user profile picture, username, tweet text, and timestamp. In other words, design the custom cell with the proper Auto Layout settings. You will also need to augment the model classes.
- User can pull to refresh.
- User can compose a new tweet by tapping on a compose button.
- User can tap on a tweet to view it, with controls to retweet, favorite, and reply.
The following optional features are implemented:
- When composing, you should have a countdown in the upper right for the tweet limit.
- After creating a new tweet, a user should be able to view it in the timeline immediately without refetching the timeline from the network.
- Retweeting and favoriting should increment the retweet and favorite count.
- User should be able to unretweet and unfavorite and should decrement the retweet and favorite count.
- Replies should be prefixed with the username and the reply_id should be set when posting the tweet,
- User can load more tweets once they reach the bottom of the feed using infinite loading similar to the actual Twitter client.
The following additional features are implemented:
- Customized launch screen and navigation bar
- Added Tab bar with options for Home and Me (current user's profile)
- Added network check and error message
Please list two areas of the assignment you'd like to discuss further with your peers during the next class (examples include better ways to implement something, how to extend your app in certain ways, etc):
- Best practices to abstract the individual actions from the cell view (reply, favorite, retweet)
- Better ways to store and display data instantaneously without having to use a network call
Here's a walkthrough of implemented user stories:
GIF created with LiceCap.
- Sometimes it was difficult to test due to the Twitter API get and update limits
- Some challenges with showing data instantaneously via the UI without doing another network call (such as the favorites and retweets counts, and the text character countdown)
- Better ways to implement and call common functions throughout the app (e.g., reply tweet)
- Some issues faced with date formatting to a specific pattern and finding the offset (time difference) using hours and minutes as units of time
- Faced some difficulties with abstracting the individual tweet actions (reply, favorite, retweet) from the cell view - the actions should be separate from the views?
Copyright 2016 Bianca Curutan Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.