Go Native and Come Back

Apr 2015

13 Mon

14 Tue

15 Wed

16 Thu 09:30 AM – 12:15 AM IST

17 Fri 09:30 AM – 12:00 AM IST

18 Sat 12:00 AM – 12:15 AM IST

19 Sun

Make a submission

MLR Convention Centre, JP Nagar

##Meta Refresh 2015 edition: The web in your pocket

##Theme
We’re already in a world where smartphones outnumber all the desktops and laptops put together. A sizeable portion of your existing user base could be accessing your website only through a handheld device. It is quite likely that future web users will never experience a site on a large screen.

Undeniably mobiles, be it phones or tablets, have become a critical channel for user acquisition and customer engagement. In fact, one can argue that mobiles are already the primary touch-point for reaching and experiencing the web in many cases.

For many web designers and developers, however, the constraints of a mobile device continue to be a beast — small screen, low resources, fickle networks and the (often false) assumption that the user is always on the move with limited time at hand.

Responsive design hasn’t been enough. Mobile-first was just a start. It takes a lot more to tame the beast and to create a great browsing experience for a mobile user.

Meta Refresh 2015 will focus on enhancing web experience on mobile devices.

We’re looking forward to proposals 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?
In your experience and practice, how does the context of mobile user influence the design of your websites? How does the behavior of users accessing web through a mobile differ?
How do you take complex web applications beyond the desktop? Speak to us from your experience.
What are the common misconceptions / incorrect assumptions about the mobile context? How did you figure these in your practice?
How do you design content for mobile websites? What kind of detailing is involved here?

And oh, if you disagree with the theme, we’d like to hear about that as well.

We are accepting proposals under the following sections:

Design process outlining concrete steps.
Mobile website strategy.
Content design.
Design patterns.
User research and insights.
Performance and front-end tools – crisp talks only.
Maintainability challenges.

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 license. If your software is commercially licensed or available under a combination of commercial and restrictive open source licenses (such as the various forms of the GPL), please consider picking up a sponsorship. We recognize 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 2015 edition is a two-day single-track conference – 16 and 17 April. We invite proposals for:

Full-length 40 minute talks
A crisp 15-minute presentation
Sponsored sessions, 40 minute duration

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.

##Workshop proposals
If you are interested in teaching, sharing knowledge with the community and/or conducting professional trainings on CSS, front-end engineering and design, submit a proposal under workshop section. Specify past experience in teaching and conducting workshops. Even better if you share links to videos of workshops where you were an instructor.
We’ll host workshops starting October 2014 until April 2015.

###Buy tickets here: https://in.explara.com/e/meta-refresh

Hosted by

Meta Refresh

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

All submissions

Previous Next

Go Native and Come Back

Submitted Mar 8, 2015

Section: Performance – full talk Technical level: Intermediate

Lets try and make the picture clear. Currently, the concensus is that:

Native apps will always perform better than the Web
The mobile web is slow

This talk will be about my experience developing native applications and learning of things I wouldn’t normally have known had I been developing only using the web. You would know what to optimize from the tips and tricks floating around the web, but you wouldn’t really know why or how they work.

This talk will focus on things are like a native app developer’s religion, but are taken for granted by the naïve web developer. Thus, encouraging the web developer to learn and develop a native app at least once, take those learnings and use them in the web world. This talk will also go about what those learnings are, one by one.

Outline

“Go Native or Go Home”, veterans in the mobile world would often say that, as they watch the web world trying to play catch in terms of performance. This talk would talk about some low level details of programming a native app that help boost performance, the details that a web programmer wouldn’t really know unless he gets his hands dirty with some native code. These details include:

Understanding Memory - each byte on a mobile device is critical, understanding garbage collection, strong references and memory leaks
Understanding Bitmaps - optimizing images, POT (power of two) textures, sprite sheets, dithering,
Understanding Rendering - introduction to the rendering process, DOM vs canvas vs hardware accelerated canvas
Multi-threading - importance of delegating all processing work to a different thread, web-workers, parallel.js

Once you develop a native application, you can very well take those learnings and develop a web application with performance as the prime focus.

Requirements

Basic understanding of JavaScript.

Speaker bio

My name is Himanshu and I’m a front-end developer at Wingify. I’m also a iOS game developer part time. I have experience with developing both native applications (games) and mobile web applications, and can present the best of both worlds to the listeners.

Links