Skip to main content

iOS 7 Will Introduce Flickr, Vimeo Integration



Apple’s iOS 7 could introduce deep integration with Flickr and Vimeo, similar to how Twitter and Facebook are currently built into the company’s mobile ecosystem. According to9to5Mac, those partnership talks first mentioned back in April are turning up some exciting opportunities for the two companies; Flickr would be a huge one for both, especially since Yahoo just announced 1TB of free storage for every Flickr user.
Presumably, users will input their Flickr/Vimeo credentials into the settings menu and then have the option to upload photos and videos directly from the iOS Photos app. That simple integration is a no-brainer, and would quickly grow Flickr’s forgotten photo-sharing emporium. Apple’s iPhone is already the most popular method for shooting photos—adding Flickr integration would instantly spike the device’s presence up even more.


Vimeo integration would work in a similar fashion, giving users the option to upload immediately after a video is recorded. It’s no YouTube—you can always use YouTube Capture for that—but it introduces a separate option that would certainly increase the popularity of the oft-overlooked video-sharing platform. Both Flickr and Vimeo already offer integration in OS X, and this only seems like a natural extension.
Being able to instantly upload photos and videos to well-known services can provide more opportunities for users to share, and it’ll free up much needed space on an actual device. Not only that, but integration would likely boost the profile for each service, and especially give Flickr a big uptick in traffic. That 1TB of free storage certainly doesn’t hurt and is pretty darn enticing.
9to5Mac does note that the features, if not fully ready, could be removed prior to Apple’s WWDC in June. With rumors that Apple and Yahoo were in discussion to introduce deeper integration between the two companies, Flickr and Vimeo sound like prime candidates. Now if only Yahoo’s new weather app would get more deeply integrated into iOS 7.
SOURCE 9TO5MAC

Comments

Popular posts from this blog

WPF-MVVM: RelayCommand Implementation

In WPF if we are implementing MVVM pattern then we need to play with Command rather than Events. You can use ICommand interface to create each command class. Implementation of ICommand in a class gives you CanExecute(), Execute() methods which take part in the action performed by Command.   Rather than making Command Class for each Command we can implement a generic Relay Command to get Command. Below is a RelayCommand class that we will implement.   ///   <summary>      ///  To register commands in MMVM pattern      ///   </summary>      class   RelayCommands  :  ICommand     {          readonly   Action < object > _execute;          readonly   Predicate < object > _canExecute;  ...

.Net List with Changed event

Sometimes we need a List which can notify user when an item is added. Here is the way that you can implement a generic ArrayList which notifies user at the time of an element is added.   using  System; using  System.Collections; namespace  ArchiveData.Logging {    // A delegate type for hooking up change notifications.    public   delegate   void   ChangedEventHandler ( object  sender,  EventArgs  e);    public   class   ListWithChangedEvent  :  ArrayList   {      // An event that clients can use to be notified whenever the      // elements of the list change.      public   event   ChangedEventHandler  Changed;      public   object  NewlyAddedItem {...

What is DispatcherTimer in wpf?

DispatcherTimer When you want to set a timer working with GUI, you always come across threading problem. The problem is that if you want to send some changes to UI that is constantly/continuously changing then that will make your UI unresponsive or in other words it will hang your UI.   To overcome from this situation, WPF gives us DispatcherTimer threading functionality that will take care of such continuously changing processing on UI thread and that will not hang your UI. We can accomplish same scenario in Win Form , through System.Windows.Forms.Timer and in WPF it is System.Windows.Threading.DispatcherTimer .   Difference between DispatcherTimer and Regular timer (System.Timers.Timer) DispatcherTimer is the regular timer. It fires its Tick event on the UI thread, you can do anything you want with the UI. System.Timers.Timer is an asynchronous timer, its Elapsed event runs on a thread pool thread. You have to be very careful in your event handler...