Theme: designing for mobile, wearables and desktop
We’re already in a world where smartphones outnumber all the desktops and laptops put together. Wearables – smart watches and devices – now act as remote controls for notifications on our phones.
A sizeable portion of your existing user base could be accessing your website only through a handheld device. While it is quite likely that future web users will never experience your site on a large screen, we also have instances where users prefer to respond to notifications on their desktop. Desktop apps are not going away either.
Meta Refresh 2016 will focus on enhancing web experience on mobile, wearables and the desktop
We’re looking forward to talks about:
- Evolution of web design in your organisation: what is the context of your business and customers? Why and how did you evolve your UX strategy and practice for mobile devices, desktop and wearables?
- How do you understand your users?
- How do you acquire new users through design, especially in non-existent markets?
- How do you design content for mobile and desktop websites? What kind of detailing is involved here?
- How do you show notifications to users on all these channels – desktop, mobile and wearables?
We are accepting proposals under the following sections:
- Design process outlining concrete steps.
- Design and user acquisition.
- Content design.
- Push notifications and how design varies based on the medium?
- User research and insights.
- Performance and front-end tools – crisp talks only.
- Maintainability challenges.
- Accessibility.
- Localization.
Criteria to submit conference proposals
You must be a practising web developer or designer, and must be able to show how your own work has advanced the state of the web in the past year. You are expected to present original work that your peers — this event’s audience — recognise as being notable enough to deserve a stage. If you are excited about someone’s work and believe it deserves wider recognition, we recommend you contact them and ask them to submit a proposal.
Guidelines for submission
Every proposal MUST be accompanied by:
- A three minute preview video where the proposer gives an elevator pitch about the talk.
- Detailed outline of the talk – either in the form of draft slides, mind map and/or textual description.
- If you are proposing to speak on a topic where the code is not open-sourced yet, the editorial panel will consider your proposal only if the code is made open-source at least three weeks before the conference.
Without the above information, your proposal will not be considered for review.
If you are submitting a Workshop Proposal, you must clearly state:
- Background knowledge that participants must possess in order to attend your workshop.
- Details and links to software / packages which participants must install before coming to the workshop.
- Laptop configuration.
- Links to background reading material and GitHub repos.
- Duration of the workshop.
- Maximum number of participants who can attend your workshop.
- Instructor’s past experience with conducting workshops.
There is only one speaker per session. Workshops can have more two or more instructors.
Entry is free for confirmed speakers.
If you are an outstation speaker, HasGeek will do its best to provide a grant that covers part of your travel and accommodation expenses in Bangalore, subject to budgetary constraints. Grants are made available only to speakers delivering full sessions (40 minutes or longer) and workshops.
Commitment to Open Source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we’d like it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.
Format
The 2016 edition is a single-day, single-track conference on 17 September. We invite proposals for:
- Full-length 40 minute talks
- A crisp 15-minute presentation
- Sponsored sessions, 40 minute duration
- Workshops – 3 to 6 hour hands-on sessions
Important dates:
Deadline for submitting proposals: 29 August 2015
Conference date: 17 September
Venue
Meta Refresh will be held at the MLR Convention Centre, J P Nagar, Bangalore.
Contact
For more information about speaking proposals, tickets and sponsorships, write to info@hasgeek.com or call +91-7676332020.
Hosted by
Meta Refresh is an umbrella forum for conversations about different aspects of design and product including: UX and interaction design CMS, content management, publishing and content marketing Information architecture more
NV
Noopur Varma
@noopur_v
What I wish I knew as a newbie designer
Submitted Aug 29, 2016
Section:
Full talk
Technical level:
Beginner
As designers we see ourselves as problem solvers.
Users are the center of our interest, the kingpins, and the bedrock. We work closely with them and try to find the best possible solution for their problems. But, as newbie designers, we tend to give a backseat to other (almost equally) important things. Namely, processes and stakeholders.
As we wet our feet in the industry with our first design tasks, we’re faced with unfamiliar challenges:
- There are other stakeholders, decision makers, even designers. We need to understand what they’re good at, what our role in the process is, and find a good way to collaborate with them.
- There’s the business perspective, the perspective of our fellow designers, and time-lines for getting things done. We need to get into other people’s heads more often.
- Design feedback is difficult. Sometimes, we get a lot, sometimes, hardly any. Sometimes, it’s difficult to put even good feedback into perspective. Sometimes the feedback is only an opinion.
- We might feel caged by processes that appear to be rigid. Despite this, we need to find our own space, and prove ourselves as capable designers.
We need to know how to plough our way through these challenges. And this talk will provide insights into how. I will be talking about things like:
- How to synchronize a designer’s process with the team/company to ease collaboration
- What are some techniques we can leverage to understand different perspectives effectively
- How to regulate, organize, and prioritize design feedback, and the processes around receiving feedback?
This talk would be most beneficial to junior designers, trying to find their place in the industry, but would apply to almost everyone working in a product company facing some of these challenges.
Outline
- I’ll pick a few categories of challenges faced by newbie designers.
- For each of these categories, I will:
- Detail the perspective of a designer fresh out of grad school, or a designer new to the industry
- Contrast this perspective with what is expected in the industry.
- Enumerate and explain some techniques that one can default to, when in doubt.
- Talk about the things that we can do to help newbie designers learn and grow.
Speaker bio
Noopur is a designer at nilenso. An engineer and NID graduate, she has been a consultant and designed both web and mobile applications for various clients, small and large. Over the last two years, she’s worked on media publishing platforms, fintech, e-commerce, parenting and education.
She is a partner at nilenso, a hippie tree hugging bicycle riding cooperative based in Bangalore. She also maps trees over the weekend, volunteers at Datakind and is always doodling.
Slides
https://speakerdeck.com/noopur/what-i-wish-i-knew-as-a-newbie-designer
Comments
Hosted by
Meta Refresh is an umbrella forum for conversations about different aspects of design and product including: UX and interaction design CMS, content management, publishing and content marketing Information architecture more
{{ gettext('Login to leave a comment') }}
{{ gettext('Post a comment…') }}{{ errorMsg }}
{{ gettext('No comments posted yet') }}