At Ingress, we believe coding should be fun. For the same reason, we have setup multiple assignments for you!
Choose an assignment based on your interest/expertise. Rather than merely completing tasks/steps mentioned below, go ahead and use your own imagination to your code as good as possible!
Minimum Requirement: Before you choose assignment, please note down minimum requirement you need to meet while coding:
- UI Framework – Use Foundation 4.0 for CSS/JS. Make sure what you create looks nice!
- Responsive - Whatever you create must work on mobile devices like iPhone/Android.
- Slideshows must be responsive as well. A user should be able to use swipe gesture on smartphones to navigate in slideshow.
- Code Organisation - All 3rd party codes, library must be inside
libfolder. No unwanted files e.g. IDE files, temporary files should be committed on git-repo.
- Github Readme – Write a nice Github Readme using markdown syntax. Make sure you include demo link and links to libraries used in readme.
Web-Developer Challenges List: Complete any one from the list below
- Twitter-Timeline Challenge
- RSS-Reader to Slideshow
Please create a small PHP-script to accomplish following parts:
Part-1: User Timeline
- Start => User visit your script page.
- He will be asked to connect using his Twitter account using Twitter Auth.
- After authentication, your script will pull latest 10 tweets form his “home” timeline.
- 10 tweets will be displayed using a jQuery-slideshow.
Part-2: Followers Timeline
- Below jQuery-slideshow (in step#4 from part-1), display list 10 followers (you can take any 10 random followers).
- Also, display a search followers box. Add auto-suggest support. That means as soon as user starts typing, his followers will start showing.
- When user will click on a follower name, 10 tweets from that follower’s user-timeline will be displayed in same jQuery-slider, without page refresh (use AJAX).
Part-3: Download Tweets
- There will be a download button to download all tweets for logged in user.
- Download can be performed in csv, xls, google-spreadhseet, pdf, xml and json formats. Show user these options.
- For Google-spreadsheet export feature, your app-user must have Google account. Your app should ask for permission to create spreadsheet on user’s Google-Drive.
- Once user click download button (after choosing option) all tweets for logged in users should be downloaded.
All parts are must. Feel free to add any extra functionality you want to make it better!
RSS-Reader to Slideshow
Here you will be creating something like Google Reader!
- Create a 2-column design. Like Google Reader.
- Left-side i.e. sidebar have a submit button to add feed URL. You should use feed detection technique. It means, if I add http://ingressit.com, feed-reader will find-out feed-URL.
- Left-side i.e. sidebar will list added feeds. A user can add multiple feeds.
- Right-side i.e. main area will show slideshow for recently added feed. It we click on a feed-link in left-side, it will show slideshow for selected feed. There may be loading time between 2 feeds which is fine.
- Parse titles & description of each post.
- Parse content-part of each post to extract first image tag . You can use regular expression pattern here.
- Output 10 titles along-with image thumbnails as HTML.
- Thumbnail must be of size 180x180px. Resize thumbnail in PHP. If you resize large images using HTML width and height, your application will be rejected right-away.
- So each slide in slideshow will have a thumbnail, post-title and description (upto 150 chars).
- Title & Thumbnail must be clickable.
Part-3: Download PDF
- Below slideshow there will be a download PDF button.
- When user clicks download button, a PDF will be created on server with slideshow content.
- Preserver formatting, clickable links inside PDF.
- Some assignments have multiple parts. You must complete all parts.
- Use of Google is allowed & encouraged.
- You are also free to use 3rd party libraries. But please mention if you use them.
For code-review, you must use Github.
- Create a free account on Github (if you do not have an account there!)
- Create a git repo for your code (ask Google for how-to in case you have never used git before)
We will only review your codes from Github. So do NOT email your codes to our HR Team!