Yes, there are some tasks, but they somewhat conflicts with current company goals and he is not sure what will come next (let's say it is clear that for 3-4 months there are some tasks, but then nothing interesting)
My first scala - play framework project, first toy that tried to do something real, was an excruciatingly mind numbingly boring engineering raw data form entry page (like only the C and R letters of CRUD). Playing with a new framework for a demo/mock up was huge fun.
Beware of the danger of the well known business anti-pattern where the "mock up" "demo" magically gets promoted to "production" when things spiral out of control and then things really hit the fan when it breaks or the requirements expand beyond all imagination. "This temporary mock up will be deleted on June 1st" or whatever probably needs to be on every page and in every header.
Sounds to me like this is a deeper issue around control and management and boring is just the excuse to not work on something s/he doesn't appreciate being "arbitrarily" forced to work on. (Do they understand and agree with the company focus? Understand being the more important word).
This also makes me wonder if there is a communication barrier that prevents genuine dialogue.
My gut tells me that you probably won't agree with me or change...so it's probably best for both of you to let him/her go.