Time spent: 14 hours spent in total
The following required functionality is completed:
- Hamburger menu
- Dragging anywhere in the view should reveal the menu.
- The menu should include links to your profile, the home timeline, and the mentions view.
- The menu can look similar to the example or feel free to take liberty with the UI.
- Profile page
- Contains the user header view
- Contains a section with the users basic stats: # tweets, # following, # followers
- Home Timeline
- Tapping on a user image should bring up that user's profile page
The following optional features are implemented:
- Profile Page
- Implement the paging view for the user description.
- As the paging view moves, increase the opacity of the background screen. See the actual Twitter app for this effect
- Pulling down the profile page should blur and resize the header image.
- Account switching
- Long press on tab bar to bring up Account view with animation
- Tap account to switch to
- Include a plus button to Add an Account
- Swipe to delete an account
The following additional features are implemented:
- List anything else that you can get done to improve the app functionality!
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):
- I used the NSNotificationCenter a lot for navigation between the different navigation controllers - was this a good idea?
- How did you pass data from view to view with this custome view controller?
Here's a walkthrough of implemented user stories:
GIF created with LiceCap.
Describe any challenges encountered while building the app.
Copyright [2017] [Tyler Lewis]
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.
Original README for part 1 of this Twitter project below...
TwitterClient is a basic twitter app to read and compose tweets from the Twitter API.
Time spent: 20 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:
- List anything else that you can get done to improve the app functionality!
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):
- How to build/extend reusable components, such as the profile picture and icons...I duplicated some code that should be moved into its own component
- How do I make a proper config file, or manage different environments? I ran into this thinking about how to manage the Twitter api keys
Here's a walkthrough of implemented user stories:
GIF created with LiceCap.
Describe any challenges encountered while building the app.
If given more time, there are a few things I'd like to refactor. I'd like to move the profile image and icons code into their own components, to avoid duplicating code. Also, there are some places I duplicated Twitter client api call code, where these could be moved into the Tweet class
To run this app locally, you must create a Keys.plist file in the Twitter group, with two keys... twitterConsumerSecret and twitterConsumerKey from your Twitter app.
Copyright [2017] [Tyler Lewis]
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.