Where the design community meets.
Karlsruhe | Germany Digital Design Nomad Joined about 3 years ago
Can i ask how old are you guys? Because everybody born in the 80s will love this, so.
I see it that way. There is something to discover, i guess everyone who is interessted in this conference will digg deep into this website, so i like the fact that it got that deepness, resembles point click adventure to me.
Thanks for the article, bookmarked it, but i think this thread is not a question right? Because you deliver the answer already :-D
Some say they are one of them: Ueno But i dunno.
Prototyping on Paper (POP) should do that. If you need easy screen to screen flows. Just saw it is bought by Marvel. So Marvel is the way to go ;-)
It might be. By the release of the first iphone it was the conceptual idea of apps in general for iOS but they switched to native development of apps beause of the idea of an appstore and the earnings of that. Another reason might be the performance of these apps.
In the end it is depending on the companys of the OS to give the browser components its power and flexibilty for apps. It has been done a lot. But this technologie is a combination of a lot of technologies which needs to be close enough to deliver a strong performance like a native app would do. We are close i think.
Currently i work on a projekt a marketplace. They use their chechkout system always in webviews. Because they just have to control and develop one payment process instead of more. A lot of apps do this.
An aspect of it is to consider that we as designer will write down the truth which is gathered by different channels (marketing, dev, technology, strategy,etc) and that has to be pushed to the dev stage on a certain date.
We are in times the people who walk around and talk to everybody to create the best solution which is time consuming because they have also to double check. A lot of could be done in PM teams. The brief and the technology reconsiderations are crucial. Besides that, the fact that we heve to check wih these channels the task or the objective is sometimes completly different. In most times the technological foundation and architecture of the application is the sorce of problems. In terms of don‘t touch that because everything will blow up (Upload Component for Images, true story)
Sometimes designers have to workout of the box, because technolgy or perspectives change.
Maybe the frame rate is the issue here, try do your animation at 60fps. Just thought about because you mentioned the hectic of it.
I think before we can help you we need more informations.
In the end you will need structure for a design/conception process and as an output an design system which will play back in future. If you start right with your system it will help a lot down the road.
There are several aspects to look on, for example:
Give your bosses an overview on the current state and tell them what can be done (New features) in a short time and why others cannot be done because of "insert soemthing here*
They should decide what you should do next. Take on new features or build it right. I think you can do that in parallel. Push new features so you will learn how they did it now. After some new features, establish your processes and system.
hop i could help.
Had the same feels. Have read Rework, changed everything. Now i am a better designer not a visualizer anymore. I think in problems instead of nice cool pictures, where devs say no.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.