Whenever possible, it’s a good idea to make your web apps work offline. Web apps will adjust to different screen sizes, resolutions, and capabilities. The same web app may respond differently depending on the device accessing it. Web apps running on the desktop may access a webcam or a local hard drive. Web apps running on your phone can access your camera, your address book, internal storage, and GPS location information. SchoolPress will have admins controlling the inner workings of the app, teachers setting up classes, and students participating in class discussions. They also have a username that identifies their activity within the app. When logged in, SchoolPress users can see which discussions are unread. This information is used to facilitate the main tasks of the app and enable a persistent experience. Logins and accounts allow a web app to save information about its users. However, the apps themselves present a way of browsing content different from the typical web browsing experience. A typical session with a Facebook or Twitter app involves about 90% reading. SchoolPress users comment on class discussions. Remember, web apps are “designed to help the user to perform specific tasks.” Google Maps users get driving directions. Examples include toolbars, drag and drop elements, rich text editors, and sliders. Web apps will have even more interactive UI elements. Forms allow users to interact with a site using something more than a click. An example would be a contact form on a website or an application form on the careers page of a company website. Websites with forms offer transactional experiences. Web apps can have links and scrolling as well, but will tend to use other methods of navigating through the app. A typical website experience involves navigating through page loads, scrolling, and clicking hyperlinks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |