You have not mentioned your years of experience.
If you have done about 2-4 years of development, it can be a good step to move into maintenance, get to understand the architecture, check how things are done for a particular use case, learn the design patterns used. All this will eventually help in designing a big architecture.
Also in maintenance depending on the maturity of the product , the fix sizes may not be more than 10 lines of code. I maintain a mobile web browser, which is a fairly huge application, but most of my fixes in the past one year have been within 10 lines of code.So it's more detective work to find out the root cause of the issue and then small surgical patches to fix it.
But if you are 7-8 years experienced, then better not to move to maintenance , as it will only frustrate you.
Also make sure that you get out of the project once you have understood the architecture, which I assume would happen within an year or two(again depends on the application architecture size). If you stay longer than that, it can put into the maintenance frame of mind, where in one just writes small patches of code to fix issues & writing large chunks of code becomes a challenge.