Apex JSON App/Content Challenge


Apex JSON App/Content Challenge

Starting with the Winter '12 release, Apex includes native support for JavaScript Object Notation (JSON). Using Apex JSON classes, your Apex code can now parse JSON content and serialize Apex objects into the JSON format. The addition of native JSON support provides many benefits for Apex development, including efficient processing of JSON for HTML5 apps.

In this challenge, we want you to write a detailed "Getting Started" article on the use of Apex JSON.

  • Start the reader with some basics and context for JSON and why it's important these days.
  • Build your article around a demo app that uses the native Apex classes for exposing methods for JSON serialization and deserialization (e.g., System.JSON, System.JSONGenerator, System.JSONParser).
  • Make sure that your demo app calls a web service to send/receive JSON. We want to demonstrate real-life scenarios here.
  • Thoroughly explain your code, what you are doing, and why you are doing it. Don't assume that the reader can read your mind ;-)

> Back to Developer Content Challenge Home Page

Challenge Requirements

Here's what we're looking for in this challenge.

General

For this challenge, you'll need to build an interesting app/tool that leverages Apex JSON and then write an article that explains its source code.

Code

  • Illustrates best practices.
  • Code can be deployed in a clean Developer Edition org, if necessary.
  • Make sure everything works ;-)
  • 85% code coverage, as necessary.

Article

Dates

This contest is now closed.

  • Start Date: January 31, 2012
  • End Date: 11:59PM Pacific Time, February 14, 2012. No exceptions.
  • Award Date: No later than 12AM Pacific Time, February 29, 2012

Prizes

The winning entry will receive a US$1000 gift card and the associated content will be published on Developer Force.

Submission Details

See Developer Contest Rules for eligibility requirements and other details.

1. Send an email with the following.

  • Subject: Apex JSON App/Content Challenge Submission
  • To: editors@developerforce.com
  • Body: Your contact information, including full name, address, and preferred email address.

2. Attach a zip archive with any supporting source code, documentation, and the article.

3. Look for a receipt of submission from us within 24 hours.

You may receive feedback on your initial submission to help you improve your work before making your submission final. Your final submission will be judged by a panel of peers based upon this scorecard.

Helpful Info

Challenge Scorecard

Here is the weighted criteria that judges will use to score submissions for this challenge.

Requirements (20%)

  • The solution addresses all the requirements as specified in the project posting request. The reviewer must be able to find all of the requirements implemented in the returned solution. (1 - 4)
  • Is the code appropriately scoped? Does is it not over design for the current task? (1 - 4)

Documentation/Readability (30%)

  • An article with the submission. The article is well-written and clearly articulates the steps necessary to deploy the system. (1 - 4)
  • The code is clear, well-written and documented clearly. (1 - 4)
  • All hard-coded values are called out directly in the deploy document. Clear instructions for replacing all hard coded values are present. (1 - 4)
  • Is the code well documented? Are there code comments where necessary? (1 - 4)

Code Quality (30%)

  • Is the code appropriately batched? Code should not be operated on individual items if possible. (1 - 4)
  • Is the code thoroughly covered with clear, functional unit tests? (1 - 4)
  • Does the code successfully deploy into a clean Developer Edition org? (1 - 4)

Innovation (20%)

  • Does the application match all of the expected functionality and exceed expectations. (1 - 4)