Improve wording and content

README.md

@@ -1,27 +1,29 @@
 # Confi Concept and Context
 
-For the	[33C3](https://events.ccc.de/congress/2016/wiki/Main_Page) I was adapting [tuxmobil's FahrPlan application](http://github.com/tuxmobil/campfahrplan) to the 33C3 as he did not want to do it this year like he did in the years before. At this point I want to thank him for all his work on this application over the years! I have seen some talks that were really important to me and I might have missed otherwise.
-In the process of adapting the application I used the aggregated schedule data from [c3voc](https://c3voc.de) because I want to attend more sessions that are not in the main halls. The presentations in the main halls are recorded and I can enjoy them at home in a calm mindset and do not have to waste precious conference time. I got great feedback about this and attended more sessions outside the main schedule than ever before.
-For the	34C3 I want to write a new application from scratch as I have some ideas that are really hard to retro-fit into the old application architecture. A rewrite from scratch will be faster and more fun. Here I will collect some ideas and corner-stones.
+For the	[33C3](https://events.ccc.de/congress/2016/wiki/Main_Page) I was doing the 33C3 adoption for [tuxmobil's FahrPlan application](http://github.com/tuxmobil/campfahrplan) as he did not want to do it 2016 as he did in the years before.
+At this point I want to thank him for all his work on this application over the years! I have seen some talks that have been really important to me that I might have missed if this app would not have been on my side at the event.
+In the process of adapting the application I used the aggregated schedule data from [c3voc](https://c3voc.de) because I want to attend more sessions that are not in the main halls. The presentations in the main halls are recorded anyway. So I can also enjoy them at home in a calm mindset and do not have to waste precious conference time. I got great feedback about this "feature" and attended more sessions apart from the main schedule than on all congresses before.
+For the	34C3 I want to write a new application from scratch as I have some Ideas that are really hard to retro-fit into the old application architecture. A rewrite from scratch will be faster and more fun. Here I will outline some ideas, insights and corner-stones.
 
-## Multi-phase conference
+## Multiple phases
 
-The conference has multiple phases:
+A Conference has multiple phases:
 
- * Conference preparation ( [HalfNarp](http://halfnarp.events.ccc.de) / [SCR](https://github.com/ligi/SCR) )
- * Attending the conference ( timeline / notifications / favorites .. )
- * Post-processing the conference ( recordings / feedback )
+ * Conference preparation (see [HalfNarp](http://halfnarp.events.ccc.de) / [SCR](https://github.com/ligi/SCR) )
+ * Attending the conference (TimeLine / notifications / favorites ..)
+ * Post-processing the conference (recordings / feedback)
 
-This should not be reflected via different applications like it is implemented right now. This gets rid of the overhead of data-sharing between the applications and provides a way better user experience.
+This should not be reflected by different applications like it is the state of the art. If all phases are addressed with the same app we get rid of the the need and overhead to share data between the applications. This does not only reduce code complexity, but also provides a significantly better user experience.
 
 ## Use RecyclerView for the timeline
 
-Adding all the other tracks did not only have these nice advantages. It on the other side made the application really slow in some cases. Especially to the conclusion of the congress when more and more sessions where added. I think by using a RecyclerView ( at least the concept if not even the implementation from AppCompat) here - we can get speed even while we have to deal with a lot of sessions.
+Adding all the additional tracks apart the main schedule did not only have these nice advantages. On the negative side it made the application really slow in some cases. This was especially suboptimal at the conclusion of the congress when more and more sessions where added. By using a RecyclerView (at least the concept if not even the implementation from AppCompat) here we get better performance without compromising on the amount of sessions.
 
 ## Fine grain system to mark interest
 
-Interest in a talk is not a yes/no thing. There are talks you do not want to miss and there are talks that you would like to see but won't leave some interesting situation for this. This should be reflected in the system.
-For recording interest we will use data from the HalfNarp and additional user input at the conference. We will have to boil down data hard - adding all the sessions made it really difficult to get the overview. To make this a bit better we will use the data from the preparation phase a bit more. If you say at preparation for the conflict resolution in which talk you are not interested in you shall not see it in the timeline at the conference and clutter your view.
+Interest in a talk is not always clearly a yes or a no. There are talks you do not want to miss and there are talks that you would like to see but won't leave some interesting situation just to attend. This should be reflected in confi.
+For recording interest we will use data from HalfNarp and additional user-input at the conference. We will have to boil down data hard - adding all the sessions made it really difficult to get the overview. To make this a bit better we will use the data from the preparation phase a bit more. If you say at preparation for the conflict resolution in which talk you are not interested in you shall not see it in the TimeLine at the conference and clutter your view.
+UI wise I want to integrate the tinder-style selection (swipe left for interest and swipe right for no interest) that I used for the 33C3 android SCR. This really worked for me to select and browse talks in a short time.
 
 ## Continuous timeline
 
@@ -50,8 +52,12 @@ Currently to adopt the application to a Congress you have to have expert knowled
 
 ## Integration in the ticket system
 
-A lot of people do not know that there is an application for the conference in the first place. The rate might be higher at a chaos conference but still there where participants without this knowledge. I want a pointer from the [esPass](http://espass.it) to the application so more people find the application without having to poll a application store they mistrust the least.
-The solution I have in mind, currently is, that when you setup your conference in [pretix](https://github.com/pretix): you specify a pointer to the conference data that then ends up in confi offering you guidance through the conference.
+A lot of people do not know that there is an application for the conference in the first place. The percentage of attendees with this knowledge might be higher at a chaos conference but still there heve been participants without this insight. I want a pointer from the [esPass](http://espass.it) ticket for the event to the application. So more people find out about the application without having to poll a appstore they mistrust the least.
+The solution I have in mind currently: when you setup your conference in [pretix](https://github.com/pretix): you specify a pointer to the conference data that then is accessible to confi for offering you guidance through the conference.
+
+## Integration of conference navigation
+
+Recently conference navigation solutions [like c3nav](https://github.com/c3nav) became available. They should be integrated so it has the chance to become easier to find the room for the session you want to attend. This could be especially useful as the venue will very most likely not be the CCH for the 34C3.
 
 ## Kotlin