Blog Archives

Taking pics easily with #WeddingSnap

On 17th September I have taken part into WeddingSnap project as Android consultant and developer. At first, I was so confused and astonished by the idea that a guest takes pictures with his phone at a wedding. But after a few days I have noticed that this is a great idea! Far from Italian traditions, catching pics socially is a great thing because it increases and amplifies the sense of friendship and closeness between people. In fact, if you consider that we are talking about unforgettable and precious moments you’ll certain understand that the bride and groom want all best things in their precious day.

15 years ago we were used to take pictures through simple cameras but now, in an era governed by most famous social networks and technologies, we are using smartphones more and more. WeddingSnap tries to collect these special moments merging wedding’s pictures into shared album, avoiding  useless tricks to share pics between guests. Through this idea all people involved in a wedding can take and share a lot of photo shoots without caring of number limits and distribuition of them.

In just one month the Android app is grown quickly, giving to this project a great contribuition. In particular, if you decide to take a look on GooglePlay, you’ll find these new features:

  • Off-line mode: you can collect pictures without connection and upload them in another moment
  • Share: you were so marvellous at your friend wedding! Why not share that shoot on Facebook or Twitter?
  • Get it! now you can download on your phone pictures shared by other guests!
  • Fastness and responsiveness: old version of WS were too slow… and now it looks very fast!
  • Delete it! Don’t worry if you have upload the worst picture of the Wedding!
  • Several improvements on errors! have you noticed that now app is more stable?

If you aren’t ready for your first, second,….. wedding, give a look at ForeverSnap! You aren’t forced to use a wedding app if you only want to collect other events pics 😉

[TUTORIAL] Working with Fragments in a ViewPager

Android-Teacher

Android

Hi to all, it’s time to post the first android tutorial in this blog and this time  I want to talk about the comunication mechanism between Fragments (you can find my other tutorials at alchemiaandroid.altervista.org).

In this tutorial we’ll focused on a communication between two Fragment (one in the role of sender and one in the role of receiver) across a FragmentActivity, that’ll work as container and channel between them.

You’ll find the project as attachment.

Difficulty level: 3/5

Terms and Documentation that you have to know:

  • Fragment: it’s a piece of code and layout that works as it is inside a container
  • FragmentActivity: it’s a container that can ingest fragments
  • MessageLoader: in this project it’s an interface that defines a method to send a message between fragments
  • ViewPager: it’s a laoyut manager that allows user to flip with his finger between “pages”
  • FragmentPagerAdapter: it’s the adapter that’ll we associate to our ViewPager

Story:

We want to create a communication channel between two Fragments allowing our developer to pass information between them.

  • FirstFragment: it’s our receiver; it has a TextView that contains received message and a Button to reset the view.
  • SecondFragmet: it’s our sender; it has an EditText to digit our message and a Button to send it.

This goals will satisfied creating a sort of Publisher and Subscriber model between them.

ProjectEngine:

  1. Our ViewPagerActivity eats our Fragments and choses to visualize the sender as first visible fragment
  2. The FirstFragment hasn’t a message in its TextView
  3. You need to flip, with your finger or sender button, to SecondFragment
  4. Here you can write a simple message
  5. The sent message will arrive to our FirstFragment travelling through the container

Download the project related to this tutorial (link).

What do you think about this tutorial? It’s useful to solve your problems and/or curiosities?

See you next time,

Simone