What about adding some information about you in the beginning, at least I would be interested to hear a bit about the guy that is talking to me. Even if a brief bio is given by the session chair/anchorman, you could give some details on your slides, especially since the project is strongly bound to your person. E.g. where you live, what your profession is, what your photographical interests are and then why you decided to start a new project, leading to the motivation/feature list.
This is just my personal opinion/expectation, I never attended a LGM and therefore have even less experience, but I think this suggestion is valid.
Furthermore, \setbeamertemplate{navigation symbols}{}, I find them quite distracting, and unless you are going to use them …
Is there a built-in Q&A? If not, then one thing might be to explicitly ask for suggestions from attendees afterwards. For instance I’m sure among the audience there will be real experts in UI and in plenty of other areas. Some of them can probably give you quite valuable feedback about your application design.
Perhaps before the conference ends, you can also round up some novice users to use your application without you guiding them about what to do, so you can see any difficulties the users might have using your application. I’m curious to know if a novice user can easily distinguish the three layer-related toolbar buttons from the other toolbar buttons, given they’re neither grouped together nor apart from the rest.
If it helps, don’t forget that we are trying to assemble assets to help people create presentations on the github repo. Maybe there will be some things there to help you!
Also, my working outline for ideas (man I’m really late at getting my presentation together), is here:
I wanted to approach it from a very high-level overview, covering areas of most interest to the audience.
Motivation
I felt was important to describe the domain of the problem and the desire/need to produce a solution.
History
What came before and how it worked in context of the Motivation.
State
What was the state of the area being approached (and how it coincided with Motivation).
Proposed Solution
How I thought a solution could be created
Implementation
How the solution I proposed was implemented
Modifications
Changing course from feedback to tailor the solution better
Results
How did it seem to work out?
Looking Forward
Further work or future path details.
I know this seems like a lot of information, but often some things can be combined down into a single slide or two for brevity (motivation + history + state for example).
I’ve just watched the presentation from Andrea on PhotoFlow.
Man, that was really great ! Really dynamic and comprehensive presentation !
You have a fan here in Caen / France !
I want to thank @patdavid and all the other cool people that were in London yesterday and that warmly welcomed me in the PIXLS.US apartment!
Pat has been a perfect host, and even if I only could stay one short day it has been so great to meet in person many of the FL/OSS developers with which I’ve been discussing during that past couple of years.
Putting a real face on top of a nickname and talking with people face to face is always an enriching experience!