title: How Session Management approach differs in mobile native vs hybrid vs web applications?
body: <p>Wanted to discuss under-the-hood information about how session is managed in case of mobile apps - native, hybrid and web applications?</p>
  
  <p><em>Please validate below Session Management scenarios:</em></p>
  
  <p><strong>Native (Android/iOS)  application</strong></p>
  
  <ol>
  <li>Using Session Cookies: Session cookies are stored in your DefaultHttpClient object. Instead of creating a new DefaultHttpClient (AFNetworking in iOS) for every request, hold onto it and reuse it, and your session cookies will be maintained.</li>
  </ol>
  
  <p><strong>Hybrid (JET, ionic, Angular, Cordova) application</strong></p>
  
  <ol>
  <li>Use localStorage to store the user info after a successful login. On logout clear the localStorage. </li>
  </ol>
  
  <p><strong>Web-HTML5 apps</strong></p>
  
  <ol>
  <li>Attribute-SessionStorage in HTML5: Can be used by the sites to add data to the session storage, and it will be accessible to any page from the same site opened in that window i.e session and as soon as you close the window, session would be lost.</li>
  </ol>
  
  <p>Thanks and Regards,</p>
  
  <p>Rohit </p>